On this page (7 sections)
A critical cross-site request forgery (CSRF) flaw, tracked as CVE-2026-128049, affects OpenMage Magento LTS. The OAuth confirm and confirmSimple actions, in both the admin area and the storefront, accept GET requests without form-key validation, according to the GitHub advisory and the NVD record.
If you run an OpenMage store, especially one that exposes REST API access through OAuth, you should check your version and plan an update. The advisory was published on November 13, 2026.
What happened
The advisory describes a missing anti-CSRF check. Two OAuth actions, confirm and confirmSimple, exist in both the admin and storefront. They process GET requests without validating a form key, the per-session token Magento-style applications normally use to prove that a state-changing request came from the site's own page.
The advisory text lists the affected ranges as OpenMage Magento LTS before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3. The GitHub Advisory Database fields for affected and patched versions say "Unknown" and no package is listed, so rely on the version ranges in the description. The advisory is marked unreviewed by GitHub.
How the weakness works
CSRF abuses the fact that a browser automatically sends a user's session cookies with a request. If a sensitive action can be triggered by a simple link and the server does not check a secret token, an attacker only needs a logged-in person to open that link.
Per the advisory, the attacker must already hold OAuth consumer credentials. They then lure a logged-in administrator or customer to a crafted confirm URL, which authorizes the attacker's own request token. The attacker can then exchange that token at /oauth/token for a persistent REST API access token bound to the victim.
The practical effect is that the attacker gains API access acting as the victim, and the token persists after the victim's browser session ends. What that access allows depends on the victim's role and the API permissions configured. An admin-bound token is clearly the worst case. The research does not detail the exact impact beyond the token being issued.
Who is affected
- Stores running OpenMage Magento LTS older than 20.18.2 on the 20.x line.
- Stores running 21.0.0-beta1 or 21.0.0-beta2 on the 21.x line.
- Stores where OAuth consumers are configured for REST API integrations, since the attacker needs OAuth consumer credentials.
- Sites where administrators browse the web or read email while logged in to the admin panel.
The need for consumer credentials narrows the realistic exposure, but it does not remove it. Third-party integrations, agencies and former partners may hold such credentials, so review who has them.
How to check your exposure
First find your OpenMage version. From the shell on the server, in your store's root directory, this Composer command lists the installed OpenMage package if you installed through Composer. Look for the version number in the output and compare it with 20.18.2 or 21.0.0-beta3.
composer show openmage/magento-ltsIf you did not install through Composer, check the version shown in your admin panel or in your deployment's release notes. Then review which OAuth consumers exist in the admin and whether you still recognize each one.
To see whether the OAuth confirm endpoints were hit unexpectedly, search your web server access log. This read-only grep prints requests whose path contains oauth/authorize or oauth_authorize; adjust the log path to your server. Treat unfamiliar entries, especially ones with external referrers, as a reason to investigate.
grep -iE "oauth[/_]authorize|oauth.*confirm" /var/log/nginx/access.logWhat to do now
- Update OpenMage Magento LTS to 20.18.2 or later on the 20.x line, or to 21.0.0-beta3 or later if you run the 21.x beta.
- Test the update on a staging copy first, then deploy to production.
- Review OAuth consumers in the admin and remove any you do not recognize or no longer use.
- Review and revoke REST API access tokens for administrators and customers if you see anything unexpected.
- Review access logs for unusual OAuth authorization requests and unfamiliar API activity since before the update.
- Ask administrators to log out of the admin panel when not working and avoid opening untrusted links in the same browser session.
- Consider restricting admin access by IP or VPN to reduce exposure.
The upstream fix is in this OpenMage commit, and the project published its own security advisory. A VulnCheck advisory is also referenced. I could not confirm details from those pages, so read them before relying on specifics such as exact fix behavior.
Detection and monitoring afterwards
Because the result of exploitation is a persistent token, patching alone does not remove a token that was already issued. After updating, audit existing tokens and consumers and rotate credentials where in doubt. Watch for API calls from unfamiliar IP addresses and for new admin-side changes you did not make.
For general guidance on spotting compromise, see how to check if a website is hacked and what to do if your website is hacked. Online stores should also keep an eye on checkout pages for unexpected scripts; see security for online stores. A website firewall can add a layer of filtering, but it is not a substitute for updating.
What is and is not known
- Confirmed by the advisory text: the affected version ranges, the missing form-key validation on GET requests, and the token exchange path.
- Not stated in the research: any reports of active exploitation, a public proof of concept, or who discovered the issue.
- Source note: the NVD entry repeats the GitHub advisory text, so the two are one source of facts, not independent confirmations. Only one independent publisher covers this so far.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
