Loading vulnerability…
XWiki Platform before version 12.8 contains a vulnerability in the property displayer component, where improper escaping is performed. This flaw allows user-controlled input to be rendered without proper sanitization, potentially enabling the injection of malicious scripts.
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 repository is a compact, self-contained exploit PoC for CVE-2020-13654 affecting XWiki Platform versions earlier than 12.8. The repo contains four files: a detailed README describing the vulnerability and attack chain, a docker-compose lab for spinning up a vulnerable XWiki/PostgreSQL environment, a Python exploit script (poc.py), and a small requirements file. The main exploit logic is in poc.py. The exploit capability is a chained web attack: it uses an authenticated low-privilege account to store a malicious <script src="..."> tag in a profile field such as Company, then waits for an administrator to view the poisoned profile. The attacker-hosted JavaScript executes in the admin's browser, fetches the XWiki admin group page at /bin/view/XWiki/XWikiAdminGroup, extracts a CSRF token, and submits a POST that adds the attacker account to XWikiAdminGroup. This yields privilege escalation to full admin rights. The script also supports optional self-registration of the attacker account, login, payload injection, verification that the payload is stored, and operation of an embedded HTTP server that both serves /payload.js and records beacon callbacks. Repository structure and purpose: README.md documents the vulnerability, usage, and expected results; docker-compose.yml provides a reproducible vulnerable lab using xwiki:11.10.5-postgres-tomcat and postgres:13, exposing ports 8080 and 9000; poc.py is the operational exploit entry point; requirements.txt lists Python dependencies (requests, beautifulsoup4, urllib3). This is not a scanner or detection script; it is an active exploit PoC with a working payload and integrated attacker infrastructure. The exploit is operational rather than framework-based, with a hardcoded but functional JavaScript payload tailored to XWiki's admin group workflow.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.