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-73312 — Proof-of-concept and technical write-up for CVE-2026-73312, an OAuth2 refresh token replay vulnerability in XenForo before 2.3.13. Includes a Python script to test for the issue. | Kitploit
Tools/GitHubGitHub/bombobombone/cve-2026-73312
Vulnerability AnalysisExploitationWeb SecurityAuthenticationPapers & Research
GitHubbombobombone/cve-2026-73312

CVE-2026-73312

Proof-of-concept and technical write-up for CVE-2026-73312, an OAuth2 refresh token replay vulnerability in XenForo before 2.3.13. Includes a Python script to test for the issue.

View Repository
422 months agoNot yet reviewed
Share

CVE-2026-73312: Refresh token replay after access-token expiry

XenForo before 2.3.13 can leave an OAuth2 refresh token reusable when its parent access token has expired.

What happens

XenForo intentionally lets a refresh token outlive its short-lived access token. During rotation it creates the replacement token family, then asks the parent access-token revoker to consume the old family. That revoker returns early when the access token is expired, before revoking the related refresh token.

The original refresh token can consequently be submitted again, producing another independent token family with the same user and scopes. The attacker must already possess a valid refresh token (and the client secret for a confidential client). The issue extends a compromised credential's useful lifetime; it is not a login bypass or scope escalation by itself.

I reproduced the issue on XenForo 2.3.12 (build 2031270) after allowing the parent access token to expire. XenForo 2.3.13 contains the fix.

Proof of concept

python poc.py https://xenforo.example CLIENT_ID REFRESH_TOKEN --verify-me

The script submits one refresh token twice and reports whether XenForo issued two different access tokens.

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.

    795
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    520
  • 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.

    439
  • 4

    redforge

    cybersecurity91/redforge

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

    346
  • 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.

    267
  • 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.

    264

Explore all tools

Browse our collection of tools

View all tools →