CVE-2025-0924

WP Activity Log <= 5.2.2 - Unauthenticated Stored Cross-Site Scripting

2025-02-12 19:09
zer0gh0st

Strategic Overview

Status
Patched in 5.3.0
Affected Plugin
WP Activity Log
Affected Version
<= 5.2.2
CVSS
7.2High
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2025-0924
View all WP Activity Log vulnerabilities

At a glance

CVE-2025-0924 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Activity Log WordPress plugin, affecting versions <= 5.2.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.3.0; sites on affected versions should update now. Disclosed February 2025, reported by zer0gh0st.

Vulnerability Overview

The WP Activity Log plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘message’ parameter in all versions up to, and including, 5.2.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

WP Activity Log <= 5.2.2 carries this weakness at message, and reaching it takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP Activity Log the fix is 5.3.0: builds <= 5.2.2 are affected, anything from 5.3.0 onward is not.

Remediation

Update to version 5.3.0, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Activity Log 5.3.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-0924https://www.wordfence.com/threat-intel/vulnerabilities/id/91699d32-1768-4d87-a4f2-91969b3e3355https://nvd.nist.gov/vuln/detail/CVE-2025-0924

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C