CVE-2026-73310 is an incorrect authorization vulnerability in the OAuth2 token endpoint of XenForo versions before 2.3.13. The endpoint does not correctly enforce that the redirect URI supplied when exchanging an authorization code is identical to the redirect URI bound to that code during the authorization request. An attacker controlling an allowlisted redirect URI can submit a different allowlisted redirect URI during token exchange, bypassing redirect-URI binding and exchanging an intercepted authorization code.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This small repository contains a README, a Python proof-of-concept script, and a Python cache ignore rule. The executable entry point, poc.py, accepts a target base URL, OAuth client ID, valid authorization code, and alternate registered redirect URI. It submits these values to XenForo's OAuth2 token endpoint, optionally supplying a PKCE code verifier and client secret. If the target accepts a redirect URI that differs from the URI used when the code was issued, the script receives an access token, outputs a SHA-256 hash rather than exposing the token directly, and tests the token against /api/me. The PoC does not create authorization codes, register callbacks, or bypass client authentication; successful exploitation depends on access to a code and a second allowlisted callback for the same OAuth client.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An OAuth2 authorization flaw in XenForo versions before 2.3.13 that fails to bind authorization codes to the redirect URI used during authorization, enabling an attacker that controls an allowlisted redirect URI to exchange intercepted authorization codes and steal OAuth2 tokens.
An OAuth2 authorization flaw in XenForo versions before 2.3.13. It fails to bind the redirect URI used at the token endpoint to the URI recorded during authorization, allowing an attacker that controls an allowlisted redirect URI to redeem an intercepted authorization code with a different allowlisted redirect URI and steal OAuth2 tokens.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.