Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-73310 — Proof of concept and technical write-up for CVE-2026-73310, an OAuth2 authorization code redirect URI binding flaw in XenForo before 2.3.13, including reproduction steps and a Python PoC script. | Kitploit
Tools/GitHubGitHub/bombobombone/cve-2026-73310
Vulnerability AnalysisExploitationWeb Application ExploitationWeb SecurityAuthentication
GitHubbombobombone/cve-2026-73310

CVE-2026-73310

Proof of concept and technical write-up for CVE-2026-73310, an OAuth2 authorization code redirect URI binding flaw in XenForo before 2.3.13, including reproduction steps and a Python PoC script.

View Repository
272 months agoNot yet reviewed
Share

CVE-2026-73310: OAuth2 redirect URI not bound to authorization code

XenForo before 2.3.13 does not bind an OAuth2 authorization code to the redirect URI used when that code was issued.

What happens

At the token endpoint, XenForo checks that the submitted redirect_uri is somewhere in the client's allowlist. It does not compare the value with the redirect URI stored on the authorization request. A client with callbacks A and B can therefore authorize through A and redeem the code while claiming B.

An attacker must control or observe a valid code and a different callback already registered to the same client. The bug does not create a code or add a new redirect URI. It weakens the binding between the front-channel authorization and the token exchange.

I reproduced the mismatch on XenForo 2.3.12 (build 2031270): callback A issued the code, callback B exchanged it, and the resulting token authenticated as the authorizing user. XenForo 2.3.13 contains the fix.

Proof of concept

python poc.py https://xenforo.example CLIENT_ID AUTHORIZATION_CODE https://client.example/callback-b --code-verifier VERIFIER

Use --client-secret for a confidential client. A vulnerable installation accepts callback B; a fixed installation rejects the mismatch.

References

  • CVE record
  • VulnCheck advisory
  • XenForo 2.3.13 release

Discovered by Marco Paciaroni (BomboBombone).

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →