Quick answers
- Is CVE-2026-113710 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113710 being exploited in the wild.
- How severe is CVE-2026-113710?
- Medium severity, with a CVSS score of 5.9, published 20 October 2026.
- Which products and versions are affected?
- apostrophe (npm) < 4.33.0, SEMVER:introduced=0,fixed=4.33.0.
- Is there a fix for CVE-2026-113710?
- Yes. apostrophe (npm): upgrade to 4.33.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113710 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113710?
- Check whether you run ApostropheCMS or apostrophe (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- apostrophe (npm): upgrade to 4.33.0 or later
npm install apostrophe@4.33.0
Technical details
The PATCH /api/v1/@apostrophecms/settings/password endpoint verifies the current password via verifyPassword() but bypasses the login module's failed-attempt counter, throttle, and lockout mechanisms. An authenticated attacker can submit unlimited password guesses at normal response speed (226–232 ms per attempt), whereas the login route enforces these protections. Successful guessing leads to password replacement and account takeover.
Affected products
- ApostropheCMS ApostropheCMS
Identifiers
- CVE-2026-113710
- GHSA-653j-g8j7-gh54
Timeline
- 2026-10-20: disclosed