Loading vulnerability…
CVE-2025-4126 is a stored cross-site scripting vulnerability in the EG-Series WordPress plugin through version 2.1.1. The vulnerability is caused by insufficient sanitization and output escaping of user-controlled attributes handled by the [series] shortcode's shortcode_title function. An authenticated user with Contributor-level privileges or higher can inject arbitrary JavaScript through the titletag attribute when the Classic Editor plugin is active. The injected script executes when a user accesses 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 demonstrates a Proof of Concept (PoC) for a reentrancy attack (CVE-2025-4126) on Ethereum smart contracts. The README provides detailed background, Solidity code for both a vulnerable contract and an attacker contract, and a Hardhat test script for automated testing. The main exploit logic is implemented in 'poc.py', a Python script that serves two purposes: (1) it simulates the reentrancy attack logic in Python, mimicking the vulnerable and attacker contracts, and (2) it contains platform-detection logic that downloads and executes a remote binary payload tailored to the detected OS and architecture (Windows x86_64, macOS ARM, or macOS x86_64). The script uses obfuscated base64-encoded strings to hide URLs and commands. The endpoints for the payloads are hosted on Alibaba Cloud OSS. The exploit is operational, as it provides a working payload and simulates the attack, but the actual impact depends on the nature of the downloaded binaries (not included in the repository). The repository is structured with a license, a comprehensive README, and the main exploit script.
5 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.