Loading vulnerability…
XenForo versions before 2.3.13 contain missing authorization in the ACP force-agreement controller. The controller permits an authenticated ACP administrator to access and submit force-agreement forms without enforcing the option permission declared by the associated navigation configuration. An administrator who lacks the intended permission can therefore update the global policy last-updated timestamp.
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 three-file repository contains a Python proof of concept (`poc.py`), a README describing CVE-2026-73318, and a minimal Python cache ignore file. The PoC accepts a user-supplied XenForo base URL and limited ACP username, prompts for the password, and maintains an authenticated cookie session. It extracts ACP CSRF tokens from HTML forms, logs in, checks whether the account is denied access to `/admin.php?options/`, and then invokes the privacy-policy and terms ForceAgreementController routes directly. The script classifies the target as vulnerable only when Options returns 403 while both force-agreement routes return 200 for GET and POST. Because its POST requests intentionally alter global agreement timestamps, `--confirm` is mandatory. This is a functional, state-changing authorization-bypass PoC rather than a passive detection-only script; its payload is basic and hardcoded to the two affected XenForo actions.
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.