Loading vulnerability…
A reflected cross-site scripting vulnerability affects YesWiki archived-revision handling in versions starting from 4.1.0 and fixed in 4.6.6. The issue stems from insufficient neutralization of attacker-controlled input in the time parameter, which is reflected into a hidden HTML field during archived revision processing in the page display handler. Because the input is not properly escaped before being embedded in the HTML response, a crafted request can cause arbitrary JavaScript to execute in the victim's browser within the security context of the YesWiki application.
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.
time parameter at the application or reverse-proxy layer where feasible.Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
2 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.