CVE-2025-50579
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 · uneditedA CORS misconfiguration in Nginx Proxy Manager v2.12.3 allows unauthorized domains to access sensitive data, particularly JWT tokens, due to improper validation of the Origin header. This misconfiguration enables attackers to intercept tokens using a simple browser script and exfiltrate them to a remote attacker-controlled server, potentially leading to unauthorized actions within the application.
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 confidenceA CORS misconfiguration in Nginx Proxy Manager v2.12.3 allows unauthorized domains to access sensitive data due to improper validation of the Origin header. Attackers can exploit this by tricking authenticated users into visiting malicious pages that execute browser scripts to intercept and exfiltrate JWT tokens to attacker-controlled servers.
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= 2.12.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Nginx Proxy Manager versionCheck the installed version of Nginx Proxy Manager (typically via docker container label, package manager, or admin dashboard 'About' section)Affected if Version is exactly 2.12.3 (the only affected version listed)
-
Identify CORS-enabled proxy hostsIn the Nginx Proxy Manager admin interface, review all proxy hosts and identify which ones have CORS headers enabled in the 'Advanced' or 'CORS' configuration tabAffected if Any proxy host has CORS settings configured
-
Inspect CORS Origin validation configurationFor each CORS-enabled proxy host, examine the 'Allowed Origins' or 'Access-Control-Allow-Origin' setting - check if it accepts a wildcard (*), multiple unspecified domains, or uses a loose pattern that could match arbitrary domainsAffected if Origin validation is set to accept any domain, uses a wildcard, or lacks strict domain whitelisting
-
Test Origin header processingSend a test request to a CORS-configured proxy endpoint with a malicious or arbitrary Origin header (e.g., Origin: http://attacker.com) and inspect the Access-Control-Allow-Origin response headerAffected if The response returns the arbitrary Origin in Access-Control-Allow-Origin without rejecting the request
-
Check for credential-inclusive CORS policiesInspect whether Access-Control-Allow-Credentials is set to true alongside a wildcard or multiple allowed OriginsAffected if Access-Control-Allow-Credentials is true and Access-Control-Allow-Origin is not explicitly limited to a single trusted domain
If Nginx Proxy Manager version 2.12.3 is running with CORS enabled and the Origin header validation accepts arbitrary or non-whitelisted domains, the environment is vulnerable to cross-origin token theft.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataConfigure proper CORS header validation in Nginx Proxy Manager to strictly whitelist trusted domains and reject unauthorized Origins, ensuring JWT tokens cannot be accessed via cross-origin requests.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50579 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50579 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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