Quick answers
- Is CVE-2025-53092 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-53092 being exploited in the wild.
- How severe is CVE-2025-53092?
- Low severity, with a CVSS score of 3.1, published 16 October 2025.
- Which products and versions are affected?
- @strapi/core (npm) SEMVER:introduced=0,fixed=5.20.0.
- Is there a fix for CVE-2025-53092?
- Yes. @strapi/core (npm): upgrade to 5.20.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-53092 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-53092?
- Check whether you run @strapi/core (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
- @strapi/core (npm): upgrade to 5.20.0 or later
npm install @strapi/core@5.20.0
Technical details
The vulnerability is a CORS (Cross-Origin Resource Sharing) misconfiguration in Strapi's default configuration. The product reflects the Origin request header directly into the Access-Control-Allow-Origin response header without validation, combined with Access-Control-Allow-Credentials: true. This allows an attacker-controlled website to send credentialed HTTP requests to a Strapi backend instance and read sensitive API responses. The attack requires network access to both the target Strapi instance and the ability to trick a user into visiting a malicious website, but requires no authentication or special privileges. Strapi versions prior to 5.20.0 are affected; the vulnerability is patched in version 5.20.0 and later by properly whitelisting trusted origins.
Affected products
- Strapi Strapi < 5.20.0
Identifiers
- CVE-2025-53092
- GHSA-9329-mxxw-qwf8
Timeline
- 2025-10-16: disclosed
- 2025-10-16: patched: Fixed in version 5.20.0