Loading vulnerability…
CVE-2023-5561 is an information disclosure vulnerability in WordPress. WordPress does not properly restrict which user fields can be searched through the REST API. As a result, an unauthenticated attacker can use the API in an oracle-style attack to infer the email addresses of users who have published public posts on an affected site. The issue stems from insufficient restriction of searchable user attributes exposed through REST API behavior, enabling attackers to test values and distinguish responses in a way that reveals whether guessed email data is associated with a public-post author account.
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.
3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python proof-of-concept exploit for CVE-2023-5561, a vulnerability in WordPress that allows disclosure of user email addresses via the REST API endpoint /wp-json/wp/v2/users. The main script, CVE-2023-5561.py, takes a target WordPress site URL as input, retrieves the list of user slugs, and then attempts to brute-force the domain part of each user's email address by making repeated API queries with crafted search parameters. The exploit leverages the API's search functionality to incrementally reconstruct email addresses, disclosing them if the endpoint is accessible and the vulnerability is present. The repository also includes a README.md with usage instructions and a description of the vulnerability. No hardcoded endpoints or credentials are present; the script targets user-supplied WordPress sites. The exploit is a POC and does not provide post-exploitation capabilities.
This repository contains a Python proof-of-concept exploit for CVE-2023-5561, a vulnerability in WordPress that allows for user enumeration and email address reconstruction via the REST API endpoint /wp-json/wp/v2/users. The exploit works by sending search requests to the endpoint, brute-forcing possible email suffixes and prefixes to reconstruct user email addresses. The script uses multiprocessing to parallelize requests but includes a 10-second delay between each request to avoid triggering WAFs or rate-limiting. The main entry point is poc.py, which takes a target WordPress site root URL as an argument. The exploit is a POC and does not provide a weaponized payload, but demonstrates the vulnerability's impact by extracting sensitive user information from vulnerable WordPress installations.
This repository contains a proof-of-concept exploit (poc.py) for CVE-2023-5561, a vulnerability in WordPress that allows unauthenticated attackers to enumerate the email addresses of users who have published public posts. The exploit works by brute-forcing the 'search' parameter of the WordPress REST API endpoint '/wp-json/wp/v2/users', reconstructing user email addresses character by character using an Oracle-style attack. The script is written in Python and uses multiprocessing to speed up the brute-force process. The only other file is a README.md, which describes the vulnerability and provides a reference link. The exploit requires the target WordPress site to have the REST API enabled and at least one user with public posts. No fake or destructive actions are present; the script is focused on information disclosure.
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.
2 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.