Cross-Site Request Forgery <= 1.2.4 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.2.5
- Affected Plugin
- Activity Log for WordPress
- Affected Version
<= 1.2.4- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-24982
At a glance
CVE-2025-24982 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Activity Log for WordPress WordPress plugin, affecting versions <= 1.2.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.5; sites on affected versions should update now. Disclosed February 2025, reported by KENJI YOSHIKAWA.
Vulnerability Overview
The Activity Log WinterLock plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.4. This is due to missing or incorrect nonce validation on several functions. This makes it possible for unauthenticated attackers to delete log data via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Activity Log for WordPress <= 1.2.4 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Activity Log for WordPress the fix is 1.2.5: builds <= 1.2.4 are affected, anything from 1.2.5 onward is not.
Remediation
Update to version 1.2.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Activity Log for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Activity Log for WordPress 1.2.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C