CVE-2026-25523: OpenMage magento-lts · Information Exposure
Affects OpenMage magento-ltsSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 20.16.1 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 20.16.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade magento-lts and openmage/magento-lts to 20.16.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenMagemagento-lts | Affected
| Fixed in
|
GitHubopenmage/magento-ltspkg:github/openmage/magento-ltsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.