dbcve.org
StrapiApplication

CVE-2025-53092

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to 5.20.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Strapi is an open source headless content management system. Strapi versions prior to 5.20.0 contain a CORS misconfiguration vulnerability in default installations. By default, Strapi reflects the value of the Origin header back in the Access-Control-Allow-Origin response header without proper validation or whitelisting. This allows an attacker-controlled site to send credentialed requests to the Strapi backend. An attacker can exploit this by hosting a malicious site on a different origin (e.g., different port) and sending requests with credentials to the Strapi API. The vulnerability is fixed in version 5.20.0. No known workarounds exist.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Strapi versions before 5.20.0 have a CORS misconfiguration that reflects the Origin header value in the Access-Control-Allow-Origin response without validation. This allows attacker-controlled sites on different origins (including different ports) to send credentialed requests to the Strapi API, potentially hijacking authenticated user sessions.

MitigationUpgrade to Strapi version 5.20.0 or later to remediate. No workarounds exist; organizations should prioritize this upgrade given the clear attack vector and lack of alternatives.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StrapiApplication
Affected:< 5.20.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Strapi version
    Run 'npm list @strapi/strapi' or check package.json for the @strapi/strapi version number
    Affected if Version is lower than 5.20.0
  2. Verify CORS middleware is present
    Check if the @strapi/middleware-cors package is installed by running 'npm list @strapi/middleware-cors' or inspecting node_modules
    Affected if CORS middleware is installed and active (required for the vulnerability to apply)
  3. Inspect CORS configuration
    Examine the Strapi configuration file (config/middlewares.ts or config/middlewares.js) for the CORS middleware configuration section
    Affected if The CORS middleware allows any origin (null, '*', or reflects the Origin header without validation) rather than whitelist only trusted domains
  4. Test CORS behavior with arbitrary origin
    Send a curl request to the Strapi API with an arbitrary Origin header (e.g., 'curl -H "Origin: https://evil.com" -I https://your-strapi-instance.com/api/...') and inspect the Access-Control-Allow-Origin response header
    Affected if The response includes the arbitrary Origin value in Access-Control-Allow-Origin without being a trusted domain

You are affected if Strapi version is below 5.20.0 AND CORS middleware is enabled AND the configuration reflects arbitrary Origin headers without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.20.0 or later
Fixed in 5.20.0
Interim mitigation

Upgrade to Strapi version 5.20.0 or later to remediate. No workarounds exist; organizations should prioritize this upgrade given the clear attack vector and lack of alternatives.

Recommended fix High confidence

5.20.0

  1. 1. Review the current Strapi version by checking package.json or running `npm list strapi`
  2. 2. Create a backup of your current project including database and configuration files
  3. 3. Update the Strapi dependency in package.json to version 5.20.0 or later: `npm install @strapi/[email protected]` (or update all @strapi/* packages to 5.20.0)
  4. 4. Run `npm install` to install the updated packages
  5. 5. Review the changelog for version 5.20.0 for any migration requirements
  6. 6. Test the upgrade in a staging environment before deploying to production
  7. 7. Deploy the upgraded version to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Strapi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53092 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data