Loading vulnerability…
XenForo versions before 2.3.13 contain a missing authorization flaw in the ACP cache-rebuild dispatcher. An authenticated limited administrator holding the rebuildCache permission can submit an arbitrary job class and actor user identifier, causing the dispatcher to invoke approval-queue functionality without enforcing the approval-queue or moderator permissions normally required. The selected actor identity is also used for moderation-log attribution.
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 small repository contains a README, Python proof of concept, and a Python cache ignore rule. The sole executable, poc.py, is a command-line authenticated exploit for CVE-2026-73317 affecting XenForo versions before 2.3.13. It uses Python standard-library HTTP, cookie, HTML, and regular-expression modules to establish an ACP session, obtain anti-CSRF tokens, and submit a cache-rebuild request naming the user-triggerable XF:ApprovalQueueProcess job. The request supplies both an arbitrary asUserId and an approval action for a chosen moderated user, then follows the generated job identifier to execute it. The PoC intentionally requires --confirm because it changes approval state, and reports success when direct approval-queue access is denied (403) but the queued job runs successfully (200). It is an active state-changing authorization-bypass exploit rather than a passive detector.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.