Loading vulnerability…
The jonkastonka Cookies and Content Security Policy WordPress plugin through version 2.29 contains incorrect access control in an AJAX consent-data endpoint. Remote attackers can invoke the unauthenticated functionality repeatedly, causing unlimited database write operations and exhausting database-server resources.
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 provides a proof-of-concept (PoC) exploit for CVE-2025-51529, a denial of service (DoS) vulnerability in the 'Cookies and Content Security Policy' WordPress plugin (by jonkastonka) through version 2.29. The exploit leverages incorrect access control in the plugin's AJAX endpoint, allowing unauthenticated remote attackers to send unlimited POST requests to '/wp-admin/admin-ajax.php' with the 'action=cacsp_insert_consent_data' parameter. Each request causes a new row to be inserted into the database, rapidly increasing its size and exhausting server resources (CPU, disk I/O). The repository contains two files: a README.md with detailed vulnerability and usage information, and 'payload.py', a Python script that launches a multi-threaded DoS attack against the vulnerable endpoint. The script allows the user to specify the target URL and number of threads, and visualizes the attack's impact on response time and database growth. No detection or fake code is present; this is a functional DoS exploit PoC.
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.