Account enumeration via reset-request timing discrepancy
Published Apr 15, 2026 · Updated Apr 15, 2026
Observable timing discrepancy in ApostropheCMS before 4.29.0 allows remote attackers to enumerate valid usernames and email addresses. The reset-request handler gives nonexistent accounts a fixed two-second delay, while valid accounts trigger MongoDB and SMTP work without equal timing normalization. Exposure requires the nondefault passwordReset option; the disclosure supplies confirmed accounts for credential stuffing or targeted phishing.
Summary
What happened
Observable timing discrepancy in ApostropheCMS before 4.29.0 allows remote attackers to enumerate valid usernames and email addresses. The reset-request handler gives nonexistent accounts a fixed two-second delay, while valid accounts trigger MongoDB and SMTP work without equal timing normalization. Exposure requires the nondefault passwordReset option; the disclosure supplies confirmed accounts for credential stuffing or targeted phishing.
The record
- CVE
- CVE-2026-33877
- Published
- Apr 15, 2026
- Updated
- Apr 15, 2026
- Vendor
- ApostropheCMS
- Product
- ApostropheCMS
- Classifications
- CWE-208, T1087
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2026CVE publishedPublication date reported by the CVE source.
- Apr 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.29.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Upstream reset-request timing proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo