XenForo before 2.3.13 contains a refresh token replay vulnerability that allows attackers to reuse a refresh token multiple times by exploiting the failure to mark tokens as consumed when the parent access token has expired. Attackers can repeatedly submit the same refresh token to generate additional independent token pairs, achieving persistent unauthorized access for the token's full lifetime.
CVE-2026-73312
Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-08. a secondary CVSS source baseline 7.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity74% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
September 8, 2026
Last Modified
September 11, 2026
Advisory Details (1)
Auto-updated Sep 8, 2026XenForo < 2.3.13 Refresh Token Replay via Expired Access Token | Advisories | VulnCheck
https://www.vulncheck.com/advisories/xenforo-refresh-token-replay-via-expired-access-tokenVendor Advisories for CVE-2026-73312(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 45× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 05:14 UTCEG score recompute
- 2026-09-19 05:14 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:40 UTCGHSA enrichment
- 2026-09-18 04:06 UTCEG score recompute
- 2026-09-18 04:06 UTCGHSA enrichment
- 2026-09-17 15:32 UTCGHSA enrichment
- 2026-09-17 02:57 UTCEG score recompute
- 2026-09-17 02:57 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 14:01 UTCEG score recompute
- 2026-09-16 14:01 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 01:26 UTCGHSA enrichment
- 2026-09-15 12:52 UTCEG score recompute
- 2026-09-15 12:51 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 00:17 UTCGHSA enrichment
- 2026-09-14 11:42 UTCGHSA enrichment
- 2026-09-13 23:08 UTCEG score recompute
- 2026-09-13 23:08 UTCGHSA enrichment
- 2026-09-13 10:33 UTCGHSA enrichment
- 2026-09-12 21:58 UTCEG score recompute
- 2026-09-12 21:58 UTCGHSA enrichment
- 2026-09-12 15:02 UTCEPSS rescore
Show 20 moreShow fewer
- 2026-09-12 09:23 UTCGHSA enrichment
- 2026-09-11 20:47 UTCGHSA enrichment
- 2026-09-11 16:10 UTCEG score recompute
- 2026-09-11 16:10 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 03:35 UTCGHSA enrichment
- 2026-09-10 15:01 UTCEG score recompute
- 2026-09-10 15:01 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-10 02:26 UTCGHSA enrichment
- 2026-09-09 13:52 UTCEG score recompute
- 2026-09-09 13:52 UTCGHSA enrichment
- 2026-09-09 01:18 UTCEG score recompute
- 2026-09-09 01:18 UTCGHSA enrichment
- 2026-09-08 20:12 UTCEG score recompute
- 2026-09-08 20:12 UTCGHSA enrichment
- 2026-09-08 14:30 UTCEG score recompute
- 2026-09-08 14:10 UTCEG score recompute
- 2026-09-08 13:26 UTCEG score recompute
- 2026-09-08 13:24 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-73312?
When was CVE-2026-73312 disclosed?
Is CVE-2026-73312 actively exploited?
What is the CVSS score of CVE-2026-73312?
How do I remediate CVE-2026-73312?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73312
Is Your Infrastructure Affected by CVE-2026-73312?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.