Loading vulnerability…
WordPress through version 6.1.1 relies on user visits to trigger the execution of wp-cron.php, which is responsible for scheduled tasks including security updates. If a site receives very few visits, scheduled tasks, including critical security updates, may not execute in a timely manner. The documentation does not adequately inform administrators of this behavior or the associated security risks for low-traffic sites.
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 contains a proof-of-concept (PoC) exploit for CVE-2023-22622, a Denial of Service (DoS) vulnerability affecting WordPress up to version 6.6.1. The main file, 'CVE-2023-22622_POC.py', is a Python script that allows an attacker to send a large number of HTTP requests (GET or POST) to a specified URL, typically the 'wp-cron.php' endpoint of a WordPress site. The script uses multi-threading (default 500 threads, configurable) to maximize the request rate, potentially overwhelming the target server and causing service disruption. The script is configurable via command-line arguments for method, target URL, data payload, and thread count. The README.md provides detailed usage instructions, requirements, and context about the vulnerability. No hardcoded targets are present; the user must specify the target URL. The exploit is a PoC and does not include advanced features such as bypasses or payload customization beyond request flooding.
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.