Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25523: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in OpenMage magento-lts

0
Medium
VulnerabilityCVE-2026-25523cvecve-2026-25523cwe-200
Published: Wed Feb 04 2026 (02/04/2026, 21:21:56 UTC)
Source: CVE Database V5
Vendor/Project: OpenMage
Product: magento-lts

Description

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.

AI-Powered Analysis

AILast updated: 02/04/2026, 21:44:44 UTC

Technical Analysis

CVE-2026-25523 is a vulnerability identified in OpenMage magento-lts, a long-term support fork of Magento Community Edition, affecting versions prior to 20.16.1. The vulnerability arises from improper handling of the X-Original-Url HTTP header in certain server configurations, which allows an attacker to discover the location of the Magento admin URL without prior knowledge or authentication. This exposure constitutes an information disclosure issue categorized under CWE-200. By sending crafted HTTP requests that manipulate the X-Original-Url header, an attacker can bypass obscurity protections that typically hide the admin panel URL, thereby gaining sensitive information about the target system's administrative interface. The vulnerability does not directly compromise confidentiality, integrity, or availability of data but facilitates reconnaissance that could lead to more severe attacks such as brute force login attempts or exploitation of other vulnerabilities. The vulnerability has a CVSS v3.1 base score of 5.3 (medium), reflecting its network attack vector, low complexity, no privileges required, and no user interaction needed. The issue was publicly disclosed and patched in version 20.16.1 of magento-lts. No known exploits have been reported in the wild as of the publication date. The vulnerability’s impact is limited to information disclosure, but given the critical nature of admin URL secrecy in Magento deployments, it is a significant concern for organizations relying on magento-lts for e-commerce operations.

Potential Impact

For European organizations, the exposure of the Magento admin URL can increase the risk of targeted attacks against their e-commerce platforms. Attackers gaining knowledge of the admin URL can attempt credential stuffing, brute force attacks, or exploit other vulnerabilities in the admin interface, potentially leading to unauthorized access, data theft, or disruption of services. Given the widespread use of Magento and its forks like OpenMage in European e-commerce, especially in countries with mature online retail sectors, this vulnerability could facilitate initial reconnaissance stages of cyberattacks. While the vulnerability itself does not allow direct compromise, it lowers the barrier for attackers to identify critical administrative endpoints. This can be particularly impactful for small to medium enterprises that may lack advanced security monitoring or network segmentation. Additionally, exposure of admin URLs could contravene data protection best practices under GDPR if it leads to unauthorized access or data breaches. Therefore, the vulnerability poses a moderate risk to confidentiality and operational security of affected European organizations.

Mitigation Recommendations

The primary mitigation is to upgrade all OpenMage magento-lts installations to version 20.16.1 or later, where the vulnerability has been patched. Organizations should audit their Magento deployments to identify versions in use and prioritize patching accordingly. In addition to patching, network-level controls should be implemented to restrict access to the admin URL, such as IP whitelisting, VPN access, or web application firewalls (WAFs) configured to block suspicious requests manipulating the X-Original-Url header. Monitoring HTTP request logs for unusual or malformed X-Original-Url headers can help detect exploitation attempts. Security teams should also enforce strong authentication mechanisms on admin panels, including multi-factor authentication (MFA), to mitigate risks if the admin URL is discovered. Regular security assessments and penetration testing should include checks for information disclosure via HTTP headers. Finally, organizations should review and harden their web server and proxy configurations to ensure headers like X-Original-Url cannot be abused to reveal sensitive endpoints.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-02T18:21:42.487Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6983ba62f9fa50a62fae1dba

Added to database: 2/4/2026, 9:30:10 PM

Last enriched: 2/4/2026, 9:44:44 PM

Last updated: 2/7/2026, 2:46:08 AM

Views: 29

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats