External risk intelligence

OpenMage Magento CSRF via OAuth Authorization Enables Persistent Token Theft.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-128049

The vulnerability affects OpenMage Magento, which is a content management system and e-commerce platform. These applications are designed to be public-facing web storefronts, and the vulnerability specifically impacts storefront OAuth actions, making the affected interface a common and intended point of internet exposure for users and administrators.

Cross-site Request Forgery

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a cross-site request forgery vulnerability within OpenMage Magento's OAuth confirmation processes. The issue could allow an attacker, by tricking a user into visiting a malicious link, to gain persistent API access by authorizing a malicious request token on behalf of the victim.

  • An attacker can trick users into granting API access.
  • This could lead to unauthorized persistent access.
  • Confirm exposure to this e-commerce platform vulnerability.

Attack Path

How an attacker could exploit the issue

An attacker with OAuth consumer credentials can trick a logged-in administrator or customer into visiting a malicious URL. This URL can authorize the attacker's request token, which can then be exchanged for a persistent access token. This access token is bound to the victim and grants the attacker access to the REST API.

  • Attacker needs OAuth consumer credentials.
  • Vulnerability in OAuth confirm actions.
  • Leads to persistent API access token.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to gain persistent REST API access tokens bound to a victim's account, whether an administrator or a customer. This is possible when a victim clicks a crafted link, which then authorizes the attacker's request token, enabling them to exchange it for a long-term access token.

  • Victim OAuth tokens.
  • Luring user to crafted URL.
  • Unauthorized API access.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and platform teams are likely responsible for addressing this cross-site request forgery vulnerability in OpenMage Magento. The first practical step is to identify all instances of the affected technology, determine their exposure and criticality, and then assign ownership for remediation planning based on risk.

  • Identify accountable application owners.
  • Verify external reachability and business criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is OpenMage Magento LTS?

OpenMage Magento LTS is a community-driven e-commerce platform and content management system. It provides the essential digital storefront infrastructure for online businesses, handling complex operations like user accounts, catalog management, and API integrations that allow external applications to connect with store data.

What does CWE-352 mean for CVE-2026-128049?

CWE-352 identifies this as a Cross-Site Request Forgery (CSRF) vulnerability. It occurs when a web application processes a request without verifying that the action was intentionally initiated by the user. In this specific case, the software fails to require a secure form-key for OAuth confirmation actions, allowing unauthorized requests to appear as legitimate user activity.

How does an attacker trigger this vulnerability?

An attacker needs existing OAuth consumer credentials and must successfully lure a logged-in user to a malicious URL. The vulnerability is triggered when the victim clicks that link, which secretly authorizes the attacker's request token. Importantly, simply browsing the site or performing standard administrative tasks does not trigger the bug; the specific interaction with the crafted confirmation link is required.

Is my site relevant to this CVE?

Halo Surface Signal indicates that because OpenMage Magento is designed as a public-facing e-commerce storefront, it is frequently accessible over the internet. If you operate an instance of the affected software, your admin and customer-facing OAuth interfaces are exposed to this risk, making your environment a potential target for unauthorized API token theft.

What are the first steps to address this issue?

Begin by auditing your environment to identify all active instances of the affected OpenMage Magento versions. Once identified, evaluate the business criticality and reachability of these systems to prioritize your response. Coordinate with your platform teams to plan the necessary updates or security configurations to mitigate the risk of unauthorized API access.

References