Cyber Resilience

CVE-2026-33877

Apostrophecms ≤ 4.29.0

Public PoC
Published
15 April 2026
Modified
20 April 2026
Patch / advisory
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0037 29th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2026-33877 is a low-severity Observable Timing Discrepancy (CWE-208) vulnerability in Apostrophecms Apostrophecms. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Password Guessing (T1110.001); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain a timing side-channel vulnerability in the password reset endpoint (/api/v1/@apostrophecms/login/reset-request) that allows unauthenticated username and email enumeration. When a user is not found, the handler returns after…

more

a fixed 2-second artificial delay, but when a valid user is found, it performs a MongoDB update and SMTP email send with no equivalent delay normalization, producing measurably different response times. The endpoint also accepts both username and email via an $or query, and has no rate limiting as the existing checkLoginAttempts throttle only applies to the login flow. This enables automated enumeration of valid accounts for use in credential stuffing or targeted phishing. Only instances that have explicitly enabled the passwordReset option are affected, as it defaults to false. This issue has been fixed in version 4.29.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1087.001 Local Account Discovery
Adversaries may attempt to get a listing of local system accounts.
T1087.002 Domain Account Discovery
Adversaries may attempt to get a listing of domain accounts.
T1087.003 Email Account Discovery
Adversaries may attempt to get a listing of email addresses and accounts.
T1087.004 Cloud Account Discovery
Adversaries may attempt to get a listing of cloud accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-39857Same product: Apostrophecms Apostrophecms
CVE-2026-33888Same product: Apostrophecms Apostrophecms
CVE-2026-33889Same product: Apostrophecms Apostrophecms
CVE-2026-32730Same product: Apostrophecms Apostrophecms
CVE-2026-35569Same product: Apostrophecms Apostrophecms
CVE-2026-40186Same product: Apostrophecms Apostrophecms
CVE-2026-23892Shared CWE-208
CVE-2026-40263Shared CWE-208
CVE-2026-43606Shared CWE-208
CVE-2024-41828Shared CWE-208

Affected Assets

apostrophecms
apostrophecms
≤ 4.29.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

Developer testing can include timing analysis or side-channel test cases that reveal observable timing discrepancies.

Engineering principles can mandate constant-time algorithms and side-channel resistance so timing discrepancies are never introduced.

Requiring approved cryptographic modules and algorithms implicitly demands implementations free of observable timing leaks.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

none

Consistent reference clocks limit the attacker's ability to measure or manipulate timing differences that could reveal internal state or processing paths.

References