Skip to content

WebCritical 9.4Patch available

CVE-2026-128049

CSRF lets attackers obtain persistent OAuth API tokens via crafted confirm URLs.

How scary is it?

updated 14 Nov 2026
  • No

    Works without logging in1

    Needs a login: a basic user account (CVSS PR:L).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild

    None reported that we know of.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run OpenMage magento-lts in an affected version< 20.18.2 / >= 21.0.0-beta1 and < 21.0.0-beta3

    Vendor says fixed in: 20.18.2, 21.0.0-beta3.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. The attacker has a user account

    CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.

    Source 1

  4. A person takes an action, such as opening a link or a file

    CVSS user interaction: required (UI:P). A victim must click, open or otherwise cooperate.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed release20.18.2 / 21.0.0-beta3

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenUpgrade to 20.18.2 or 21.0.0-beta3; revoke/rotate API tokens and OAuth credentials.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Impacts widely deployed e-commerce platform (OpenMage Magento LTS). Allows theft of persistent API tokens for admins/customers, enabling account takeover and data loss; requires org-wide remediation.

CVSS
9.4Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.16%chance of exploitation in the next 30 daystop 95% of scored CVEsFIRST score of 21 Nov 2026
Fix
Fixed in 20.18.2, 21.0.0-beta3per the vendor
Published
13 Nov 2026analysed here 14 Nov 2026

Do first. Upgrade to a fixed release: 20.18.2, 21.0.0-beta3.

Summary

Impact

Attackers can obtain persistent REST API tokens for logged-in admins/customers via CSRF, enabling account takeover, data exfiltration, and unauthorized admin API actions.

Triage

Attack surface
Client-side
Exploitable
At runtime
Attack vector
network
Weakness
  • CWE-352 Cross-Site Request Forgery (CSRF)
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
OpenMage magento-lts< 20.18.2>= 21.0.0-beta1 and < 21.0.0-beta3Vendor says fixed in: 20.18.2, 21.0.0-beta3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • OpenMage Magento LTS <20.18.2
  • OpenMage Magento LTS 21.0.0-beta1 prior to 21.0.0-beta3

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The attack involves crafted URLs that exploit a cross-site request forgery vulnerability to obtain OAuth tokens. These URLs appear as normal HTTP requests, making it difficult for a firewall to distinguish malicious from legitimate traffic.

Also consider: SameSite cookies · CSRF tokens

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

Timeline

  1. 13 Nov 2026Published
  2. 13 Nov 2026CVE record last updatedsame day later
  3. 14 Nov 2026Analysed by vulneraibility.com2 days later

Common questions

Is CVE-2026-128049 being exploited?

Not confirmed. CVE-2026-128049 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.

How severe is CVE-2026-128049?

CVE-2026-128049 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-128049?

Yes. A fix has been recorded for CVE-2026-128049. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-128049 affect?

CVE-2026-128049 affects OpenMage Magento LTS <20.18.2, OpenMage Magento LTS 21.0.0-beta1 prior to 21.0.0-beta3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-128049?

Upgrade to 20.18.2 or 21.0.0-beta3; revoke/rotate API tokens and OAuth credentials.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

3 references in the CVE record, grouped by the tags the record gives them.

Advisories (2)

  • github.com /OpenMage/magento-lts/security/advisories/GHSA-grrq-9gq2-vm55
  • vulncheck.com /advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-con

Patches (1)

  • github.com /OpenMage/magento-lts/commit/1f83e49b60e08aa7ba89dcc2d41ea21f62c0b796

Also tracked as GHSA-grrq-9gq2-vm55 (OSV).

Where the data on this page comes from

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • FIRST EPSS: exploit probability and percentile
  • OSV: advisory aliases and downstream package versions

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.