cve.bz

CVE-2026-128049 OpenMage Magento LTS before 20.18.2 CSRF via OAuth Authorization Confirm

9.4 criticalEPSS 0.2%

Critical (9.4) in openmage magento-lts. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
OpenMage Magento LTS before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a cross-site request forgery vulnerability in the admin and storefront OAuth confirm and confirmSimple actions, which accept GET requests without form-key validation. Attackers holding OAuth consumer credentials can lure a logged-in administrator or customer to a crafted confirm URL that authorizes the attacker's request token, then exchange it at /oauth/token for a persistent REST API access token bound to the victim.

Severity

CVSS 4.0

9.4 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CVSS 3.1

9.0 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-128049 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128049?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128049?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-128049 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-128049

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-128049](https://cve.bz/cve/badge/CVE-2026-128049.svg)](https://cve.bz/cve/CVE-2026-128049)

HTML:

<a href="https://cve.bz/cve/CVE-2026-128049"><img src="https://cve.bz/cve/badge/CVE-2026-128049.svg" alt="CVE-2026-128049"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenMage magento-ltsbefore 20.18.2
OpenMage magento-ltsfrom 21.0.0-beta1 before 21.0.0-beta3

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON