Loading vulnerability…
In WordPress 4.7 before 4.7.1, the REST API endpoint implemented in wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php does not properly restrict access to user listings. This allows unauthenticated remote attackers to enumerate and obtain sensitive information about registered users, such as usernames and user IDs, by sending requests to the /wp-json/wp/v2/users endpoint.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (5 hidden).
This repository contains a Python proof-of-concept exploit for CVE-2017-5487, a user enumeration vulnerability in WordPress 4.7 before 4.7.1. The main file, CVE-2017-5487.py, allows an attacker to enumerate WordPress users by sending unauthenticated HTTP GET requests to the vulnerable REST API endpoints (/wp-json/wp/v2/users/ and /?rest_route=/wp/v2/users/). The script can target a single URL or process a list of URLs from a file, using multithreading for efficiency. The exploit leverages the information disclosure flaw in the WordPress REST API to retrieve usernames (and potentially other user details) from affected sites. The README.md provides background on the vulnerability, affected versions, exploitation details, and mitigation steps. The exploit is a standalone script, not part of a framework, and is operational as a proof-of-concept for information disclosure attacks.
This repository contains a Python proof-of-concept exploit for CVE-2017-5487, a vulnerability in WordPress versions 4.7.0 and 4.7.1 that allows unauthenticated user enumeration via the REST API. The main script, 'leak-wordpress-user.py', takes a list of target URLs and attempts to enumerate user names by sending GET requests to the '/?rest_route=/wp/v2/users/<id>' endpoint for each target. If successful, it extracts and saves the user ID and name to 'users_leak.txt'. The repository includes a README with setup and usage instructions, a requirements.txt for dependencies, and the exploit script itself. The exploit is network-based and targets publicly accessible WordPress sites vulnerable to this REST API 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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.