Loading vulnerability…
CVE-2025-1489 is a stored cross-site scripting (XSS) vulnerability in the WP-Appbox plugin for WordPress, affecting all versions up to and including 4.5.4. The vulnerability arises from insufficient input sanitization and output escaping in the appbox shortcode, allowing authenticated users with contributor-level access or higher to inject arbitrary JavaScript or HTML into pages. The injected scripts are executed in the context of any user who visits the affected page.
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 small proof-of-concept lab for reproducing CVE-2025-1489, described here as a stored XSS issue in the WordPress WP-Appbox plugin version 4.5.4. It is not a weaponized exploit kit; instead, it provides a controlled environment to validate that attacker-controlled shortcode input can be stored in WordPress content and later rendered in a victim browser, causing attacker-observable outbound requests. Repository structure is minimal: README.md documents the vulnerability, affected versions, and reproduction steps; docker-compose.yml builds a three-container lab consisting of MariaDB, WordPress, and a Python-based attacker server; attacker/server.py is the only substantive code file and implements a simple HTTP listener that logs GET/HEAD callbacks, including Referer and User-Agent, to /srv/requests.log; attacker/requests.log is an output artifact; attacker/test.py is effectively empty. The exploit capability demonstrated is stored browser-side execution through malicious WP-Appbox shortcode data, specifically attribute/style-context injection that results in external resource loading. The code in this repository does not generate the XSS payload automatically and does not include post-exploitation logic such as cookie theft or session hijacking. Its main operational purpose is confirmation and forensic visibility: when a vulnerable page is viewed, the victim browser contacts the attacker server, and the server records request metadata. This makes the repository a realistic but limited POC reproduction environment rather than a full exploit framework.
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.