Session reuse after API user deactivation in OpenMage magento-lts
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- Present
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-613.
Summary
OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an insufficient session expiration flaw (CWE-613). API sessions and REST OAuth tokens remain valid after the API user is deactivated or the API key is rotated. A remote attacker with high privileges and an existing session or access token can read and modify customer, order and catalog data.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an insufficient session expiration vulnerability because Mage_Api_Model_Session::_renewBySessId() never checks api_user.is_active and REST OAuth authorization never checks whether the admin user is active. Attackers holding an existing SOAP/XML-RPC session or OAuth access token retain API access after deactivation or API key rotation, reading and modifying customer, order and catalog data.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
Upgrade magento-lts to 20.18.2 if you run the 20.x line, or to 21.0.0-beta3 if you run 21.0.0-beta1.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA magento-lts (OpenMage) Fixed in 20.18.2
- Fix · CNA magento-lts (OpenMage) Fixed in 21.0.0-beta3
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
OpenMage magento-lts 21.0.0-beta3
19 records Highest priority Priority MEDIUM 3 MEDIUM, 16 LOW
Other records, highest priority first
- TI-2026-91454 File upload in OpenMage magento-lts lets attackers run codePriority MEDIUM 43
- TI-2026-91455 OpenMage magento-lts Account Takeover via Predictable Confirmation KeyPriority MEDIUM 42
- TI-2026-91457 Cross-site request forgery in OpenMage Magento LTS OAuth confirmPriority MEDIUM 40
- Release ·
OpenMage magento-lts 20.18.2
16 records Highest priority Priority MEDIUM 3 MEDIUM, 13 LOW
Other records, highest priority first
- TI-2026-91454 File upload in OpenMage magento-lts lets attackers run codePriority MEDIUM 43
- TI-2026-91455 OpenMage magento-lts Account Takeover via Predictable Confirmation KeyPriority MEDIUM 42
- TI-2026-91457 Cross-site request forgery in OpenMage Magento LTS OAuth confirmPriority MEDIUM 40
Timeline
- 2026-11-13 Threatist record created from CVE-2026-128030
- 2026-11-13 Alias added: GHSA-4wpp-3r54-34hj
References
More OpenMage vulnerabilities
- TI-2026-30484 Magento LTS: Weak API Session ID — Predictable MD5 of Time-Derived Inputs CVSS 4.0CRITICAL 9.3
- TI-2026-20633 OpenMage LTS's Phar Deserialization leads to Remote Code Execution CVSS 3.1HIGH 8.1
- TI-2026-29239 OpenMage LTS has Customer File Upload Extension Blocklist Bypass that Leads to Remote Code Execution CVSS 4.0HIGH 8.7
- TI-2023-22272 Magento LTS's guest order "protect code" can be brute-forced too easily CVSS 3.1HIGH 7.5
- TI-2026-30528 Magento LTS: Open Redirect via Unvalidated `uenc` Parameter in `stockAction()` - magento-lts CVSS 3.1MEDIUM 6.1
- TI-2026-30747 Magento LTS: Reflected XSS - Import -> Data Flow (profiles) CVSS 4.0MEDIUM 5.3
Sources
- CVE-2026-128030 · CVE Program
- CVE-2026-128030 · NVD
- FIRST EPSS
- GHSA-4wpp-3r54-34hj · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences