Loading vulnerability…
CVE-2023-36471 affects the HTML sanitizer included in XWiki Commons since version 14.6RC1. The sanitizer incorrectly allowed form-related HTML elements, including form and input, in restricted HTML. In XWiki, this permitted an attacker without script rights to embed malicious form controls in rendered content. The issue could be abused directly for phishing by presenting attacker-controlled forms to users. More seriously, in the context of a sheet rendered as part of an edit form, an attacker could inject a hidden input such as content containing XWiki/Groovy markup so that, when an administrator submits the form, the payload is processed and can execute server-side code. The flaw is therefore an insufficient sanitization/neutralization issue in XWiki's HTML filtering logic that enables dangerous HTML elements to survive sanitization and be interpreted in a privileged workflow.
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.
form, input, select, textarea, button to the xml.htmlElementSanitizer.forbidTags setting in xwiki.properties. Additionally, reduce exposure by restricting who can edit sheets or content rendered in administrative workflows and by monitoring for suspicious restricted HTML containing form controls.Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.