Skip to main content
CVE-2025-13471VulnerabilityPublished Updated

CVE-2025-13471: User Activity Log (WordPress plugin) · Insecure Direct Object Reference

Affects User Activity Log (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
User Activity LogAffected
  • <=2.2
Fixed in–

AI-suggested

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.

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)

References

Community reviews

Loading reviews…