Loading vulnerability…
The User Activity Log WordPress plugin (versions up to and including 2.2) contains an unauthenticated limited options update vulnerability in the failed-login handler function ual_shook_wp_login_failed. The handler lacks a capability check and writes attacker-controlled failed usernames directly into update_option() calls. As a result, an unauthenticated attacker can influence select WordPress site options, specifically enabling transitions from 0 to a non-zero value, and can corrupt sensitive options such as wp_user_roles, potentially breaking administrative access.
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.
0 to non-zero values, which may reopen user registration and/or corrupt critical configuration (e.g., wp_user_roles). This can cause administrative denial of service, including wp-admin lockout and disruption of normal site administration.If you can’t patch tonight, do this now.
users_can_register and wp_user_roles.Patch, then assume compromise.
ual_shook_wp_login_failed).1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Go-based exploit for CVE-2025-11877, targeting the User Activity Log WordPress plugin (versions <= 2.2). The exploit leverages a vulnerability where failed login attempts with crafted usernames can update arbitrary WordPress options due to missing capability checks in the plugin. The main exploit logic is implemented in 'main.go', which provides command-line options to enable user registration, modify arbitrary options, or simply check for plugin presence. The exploit works by sending POST requests to the '/wp-login.php' endpoint with the 'log' parameter set to the desired option name, exploiting the plugin's flawed handling of failed logins. The repository is structured with a single code file ('main.go'), a README with detailed usage and vulnerability explanation, and a .gitignore. The exploit is operational and can be used to enable user registration or corrupt site options on vulnerable WordPress installations.
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.
6 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.