Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13471: CWE-639 Authorization Bypass Through User-Controlled Key in User Activity Log

0
Medium
VulnerabilityCVE-2025-13471cvecve-2025-13471cwe-639
Published: Wed Jan 28 2026 (01/28/2026, 06:00:03 UTC)
Source: CVE Database V5
Product: User Activity Log

Description

The User Activity Log WordPress plugin through 2.2 does not properly handle failed login attempts in some cases, allowing unauthenticated users to set arbitrary options to 1 (for example to enable User Registration when it has been turned off)

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/03/2026, 03:31:38 UTC

Technical Analysis

CVE-2025-13471 is a vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting the User Activity Log WordPress plugin versions up to 2.2. The flaw stems from the plugin's failure to properly handle failed login attempts, which allows unauthenticated users to manipulate certain plugin options by setting arbitrary keys to a value of 1. For example, an attacker can enable User Registration even if the site administrator has disabled it, potentially allowing unauthorized user account creation. This bypass occurs because the plugin does not adequately validate or restrict the modification of these options, leading to an authorization bypass scenario. The vulnerability can be exploited remotely over the network without requiring any privileges or user interaction, making it relatively easy to exploit. The impact is primarily on confidentiality, as unauthorized configuration changes could lead to user enumeration or unauthorized account creation, but it does not directly affect integrity or availability. No patches or exploit code are currently publicly available, but the vulnerability is published and should be addressed promptly. The vulnerability affects a widely used WordPress plugin, increasing the risk for many websites relying on it for user activity monitoring and security auditing.

Potential Impact

The primary impact of CVE-2025-13471 is the unauthorized modification of plugin settings by unauthenticated attackers, which can lead to enabling features like User Registration that were intentionally disabled. This can increase the attack surface by allowing attackers to create accounts, potentially facilitating further attacks such as privilege escalation, spam, or phishing campaigns. While the vulnerability does not directly compromise data integrity or availability, the confidentiality of user data could be indirectly affected if attackers leverage the unauthorized registration to gain access to restricted areas or sensitive information. Organizations running WordPress sites with this plugin are at risk of unauthorized configuration changes that undermine security policies. The ease of exploitation and lack of required authentication make this a significant concern for websites exposed to the internet, especially those with high traffic or sensitive user data. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, as attackers may develop exploits in the future.

Mitigation Recommendations

To mitigate CVE-2025-13471, organizations should first verify if their WordPress installations use the User Activity Log plugin version 2.2 or earlier and plan to update to a patched version once available. Until a patch is released, administrators should restrict access to the WordPress admin dashboard and plugin settings to trusted users only, employing strong authentication and role-based access controls. Implementing Web Application Firewalls (WAFs) with rules to detect and block suspicious requests targeting plugin options can help reduce exploitation risk. Monitoring logs for unusual changes to plugin settings or spikes in user registration attempts can provide early detection of exploitation attempts. Additionally, disabling user registration site-wide if not needed and using security plugins that enforce stricter input validation can help mitigate the risk. Regular backups and incident response plans should be in place to recover quickly if unauthorized changes occur.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2025-11-20T08:38:24.493Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6979aac84623b1157c94fc41

Added to database: 1/28/2026, 6:20:56 AM

Last enriched: 4/3/2026, 3:31:38 AM

Last updated: 5/9/2026, 6:09:16 PM

Views: 152

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses