PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-73310 – OAuth2 Token Theft via Redirect URI Bypass – XenForo before 2.3.13

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-73310 is an authorization flaw (CWE-863: Incorrect Authorization) in the OAuth2 token endpoint of XenForo forum software, affecting all versions before 2.3.13. An attacker who controls any allowlisted redirect URI for an OAuth2 client can bypass redirect URI binding during token exchange, enabling theft of OAuth2 tokens from intercepted authorization flows. The flaw carries a CVSS v4.0 base score of 8.2 (High).

Technical details

  • Root cause: the OAuth2 token endpoint fails to strictly bind the redirect_uri supplied during the token exchange to the one recorded at authorization time.
  • Trigger condition: an OAuth2 client must have more than one allowlisted redirect URI, and the attacker must control (or be able to intercept traffic to) at least one of those allowlisted URIs.
  • Attack vector: network, no privileges or user interaction required beyond the victim completing a normal OAuth2 authorization flow; the attacker submits a different allowlisted redirect URI than the one used originally to complete the token exchange.
  • Impact: theft/interception of OAuth2 access tokens, allowing an attacker to impersonate the victim to the relying application without needing to compromise the victim’s XenForo credentials directly.

Affected software

  • XenForo (forum software), all versions prior to 2.3.13, when the OAuth2 authorization server functionality is in use.

Severity

  • CVSS v4.0: 8.2 (High) — CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 5.9 (Medium) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: upgrade XenForo to version 2.3.13 or later, which corrects the redirect URI binding logic in the OAuth2 token endpoint.
  • If unable to patch immediately: restrict each OAuth2 client to a single, tightly-controlled redirect URI where possible, and audit existing OAuth2 client configurations for unnecessary or broadly-scoped redirect URI allowlists.
  • Review OAuth2 client logs for token exchanges using redirect URIs that differ from the URI used at the initial authorization request.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: jQuery.extend(true, XenForo, Forum software by XenForo™, <!--XF:branding, <html id="XenForo", <html id="XF"
  • JavaScript object present once the page runs: XF.GuestUsername

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge