Quick answers
- Is CVE-2026-113660 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113660 being exploited in the wild.
- How severe is CVE-2026-113660?
- Medium severity, with a CVSS score of 4.3, published 20 October 2026.
- Which products and versions are affected?
- ApostropheCMS Apostrophe versions prior to fix; apostrophe (npm) < 4.33.0, SEMVER:introduced=0,fixed=4.33.0.
- Is there a fix for CVE-2026-113660?
- 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-113660 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-113660?
- Check whether you run ApostropheCMS Apostrophe 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 exist-in-locale API endpoint performs a direct database query based on user-supplied document IDs, locale, and mode parameters without applying document-level authorization checks. An authenticated attacker can bulk-probe arbitrary document IDs to determine existence, locale availability, and draft status. The endpoint returns localized document identifiers that would be rejected by the normal page API, creating an authorization bypass via information disclosure.
Affected products
- ApostropheCMS Apostrophe versions prior to fix
Identifiers
- CVE-2026-113660
- GHSA-vmxh-77cw-65j7
Timeline
- 2026-10-20: disclosed