Loading vulnerability…
CVE-2026-73312 is a refresh-token replay vulnerability in XenForo versions before 2.3.13. When an access token associated with a refresh token has expired, XenForo fails to mark the refresh token as consumed following its use. An attacker can therefore replay a previously obtained refresh token repeatedly, with each successful exchange producing an independent access-token and refresh-token pair.
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.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This three-file repository contains a standalone Python proof of concept for CVE-2026-73312, affecting XenForo releases before 2.3.13. poc.py accepts a target base URL, OAuth client ID, and refresh token, optionally adding a confidential-client secret. It POSTs the same refresh-token grant twice to /api/oauth2/token, extracts each access token, prints only its SHA-256 digest, and flags the target as vulnerable when both requests yield different nonempty access tokens. The optional --verify-me mode sends each issued token as a Bearer credential to /api/me and checks for HTTP 200. README.md documents the affected token-family revocation logic, prerequisites, example invocation, affected/fixed versions, and references; .gitignore excludes Python bytecode artifacts. The code is a credential-replay validation PoC rather than a shell/RCE payload or a general detection-only script.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A refresh-token replay vulnerability in XenForo versions before 2.3.13. An attacker able to obtain a refresh token can reuse it repeatedly after its parent access token expires, generating independent token pairs and retaining unauthorized access for the refresh token's lifetime.
A refresh-token replay vulnerability in XenForo versions before 2.3.13. A reused refresh token can generate multiple independent access/refresh-token pairs after its parent access token expires, enabling persistent unauthorized access for the refresh token's lifetime.
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.