Loading vulnerability…
CVE-2026-73319 is a cross-site scripting vulnerability in XenForo versions before 2.3.13. The dynamic redirect handler insufficiently validates redirect targets, allowing a malicious javascript: URI to bypass host validation when the board hostname is embedded in the URI authority component. Percent-encoded newline characters can be used to evade server-side filtering. When an authenticated user performs a Follow action on the attacker-controlled link, attacker-supplied JavaScript executes in the XenForo board's origin.
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 for CVE-2026-73319, a XenForo dynamic-redirect validation flaw. README.md documents that XenForo versions before 2.3.13 accept a same-host javascript: URI because validation checks the host but does not restrict the URI scheme. poc.py accepts a target base URL and member slug, then launches a one-use local HTTP server on 127.0.0.1:8766 by default. Its sole GET response redirects the browser to XenForo's public member Follow confirmation URL with a crafted _xfRedirect parameter. On confirmation by an authenticated victim, the redirect is assigned to window.location and executes the embedded JavaScript in the forum origin. The included payload is intentionally benign and sets window.name, but demonstrates an XSS-capable execution primitive. No external exploit framework or hardcoded remote target is used.
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.