Activity Log – Monitor User and Agent Changes <= 2.13.1 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.14.0
- Affected Plugin
- Activity Log – Monitor User and Agent Changes
- Affected Version
<= 2.13.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-84759
At a glance
CVE-2026-84759 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Activity Log WordPress plugin, affecting versions <= 2.13.1. 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 2.14.0; sites on affected versions should update now. Disclosed September 2026, reported by Asim Alshaya.
Vulnerability Overview
The Activity Log – Monitor User and Agent Changes plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.13.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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 <= 2.13.1 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 the fix is 2.14.0: builds <= 2.13.1 are affected, anything from 2.14.0 onward is not.
Remediation
Update to version 2.14.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Activity Log: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Activity Log 2.14.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Activity Log – Monitor User and Agent Changes
- 8.8Activity Log 2.3.5 - 2.6.1 SQL Injection
- 8.3CVE-2022-27858: Activity Log <= 2.8.3 CSV Injection
CVE-2022-27858 - 7.5Activity Log Plugin < 2.0.4 Fulle Path Disclosure
- 7.2CVE-2024-10788: Activity Log Stored XSS
CVE-2024-10788 - 6.1CVE-2018-8729: Activity Log <= 2.4.0 Multiple Cross-Site Scripting
CVE-2018-8729 - 6.1CVE-2016-10890: Activity Log <= 2.3.2 Reflected Cross-Site Scripting
CVE-2016-10890 - 6.1CVE-2016-10891: Activity Log < 2.3.3 Cross-Site Scripting
CVE-2016-10891 - 6.1Activity Log <= 2.3.2 Reflected Cross-Site Scripting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C