CVE-2026-128045: OpenMage magento-lts · Insecure Direct Object Reference
Affects OpenMage magento-ltsSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 20.18.2 when convenient.
Data as of 13 Nov 2026, 09:59 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.3 |
- Patch
- Available – fixed in 20.18.2, 21.0.0-beta3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 13 Nov 2026.
What to do
Upgrade magento-lts to 20.18.2; magento-lts to 21.0.0-beta3; openmage/magento-lts to 21.0.0-beta3 or 20.18.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenMagemagento-lts | 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
Upgrade OpenMage Magento-LTS to version 20.18.2 or later, or 21.0.0-beta3 or later, where this vulnerability is fixed. The vendor has released official fixes in these versions. If upgrading immediately is not possible, consider disabling the order-status RSS feed feature to prevent exploitation. No other mitigations are specified.
Description
OpenMage Magento-LTS versions before 20.18.2 and 21.0.0-beta3 contain an authorization bypass vulnerability in the /rss/order/status feed. The URL key used for authorization is an unsigned Base64-encoded JSON object containing order, increment, and customer IDs. This allows unauthenticated attackers to forge keys by enumerating sequential IDs and access other customers' order details including names, items, prices, totals, and status comments when the order-status RSS feed is enabled.
References
- github.com/OpenMage/magento-lts/security/advisories/GHSA-3hh8-xg45-mwrr (opens in a new tab)
- github.com/OpenMage/magento-lts/commit/fde2d109292944d705c4035d87df055b1e945ea3 (opens in a new tab)
- vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-authorization-bypass-via-forgeable-rss-order-key (opens in a new tab)