dbcve.org
MagentoCMS · Openmage

CVE-2026-25523

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to after 20.16.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Magento-lts is a long-term support alternative to Magento Community Edition (CE). Prior to version 20.16.1, the admin url can be discovered without prior knowledge of it's location by exploiting the X-Original-Url header on some configurations. This issue has been patched in version 20.16.1.

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 · moderate confidence

Magento-lts versions prior to 20.16.1 allow unauthenticated attackers to discover the admin URL path by exploiting the X-Original-Url HTTP header. On vulnerable configurations, the server reveals the internal admin path in responses or error messages when this header is present, enabling reconnaissance for subsequent attacks.

MitigationUpgrade to Magento-lts version 20.16.1 or later. As a temporary measure, configure the web server to strip or reject the X-Original-Url header.

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
MagentoCMS
Affected:<= 20.16.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
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 checks

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

  1. Determine installed Magento-lts version
    Check the composer.json file in the Magento root directory for the 'openmage/magento-lts' package version, or look for a version indicator in the admin dashboard footer or system configuration page.
    Affected if The installed version is 20.16.0 or lower.
  2. Test for admin path disclosure via X-Original-Url header
    Send an HTTP request to the site with the header 'X-Original-Url: /admin' or a similar arbitrary path and examine the response for any mention of the actual admin URL path in error messages, redirect locations, or debug output.
    Affected if The response reveals the actual internal admin path (such as /admin or a custom admin URL) that was not explicitly requested.
  3. Inspect web server configuration for header handling
    Review the Apache (httpd.conf, .htaccess) or Nginx (nginx.conf) configuration files for any rules that process or honor the X-Original-Url header, such as RewriteRule directives using THE_REQUEST or conditions that echo back URL components.
    Affected if The web server is configured to process X-Original-Url headers in a way that can cause the server to output or reflect the admin path in responses.

You are affected if Magento-lts version is 20.16.0 or lower AND your server responds to X-Original-Url headers by revealing the internal admin path in any part of the HTTP response.

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 a release after 20.16.0
Interim mitigation

Upgrade to Magento-lts version 20.16.1 or later. As a temporary measure, configure the web server to strip or reject the X-Original-Url header.

Recommended fix High confidence

20.16.1

  1. 1. Backup your current Magento-lts installation and database
  2. 2. Download Magento-lts version 20.16.1 from the official repository
  3. 3. Replace the existing installation files with the new version, or run the appropriate update command for your installation method
  4. 4. Clear all caches after the upgrade
  5. 5. Verify the admin URL is no longer discoverable via X-Original-Url header requests
  6. 6. Test that the admin panel is accessible at the expected (intended) location

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

Fix this in Magento Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25523 — 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-2026-25523 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