WP Activity Log <= 4.5.0 - Missing Capabilities Check to User Enumeration
Strategic Overview
- Status
- Patched in 4.5.2
- Affected Plugin
- WP Activity Log
- Affected Version
<= 4.5.0- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-2261
At a glance
CVE-2023-2261 is a medium-severity Missing Authorization vulnerability in the WP Activity Log WordPress plugin, affecting versions <= 4.5.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 4.5.2; sites on affected versions should update now. Disclosed May 2023, reported by Marco Wotschka.
Vulnerability Overview
The WP Activity Log plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the handle_ajax_call function in versions up to, and including, 4.5.0. This makes it possible for authenticated attackers, with subscriber-level access or higher, to obtain a list of users with accounts on the site. This includes ids, usernames and emails.
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 interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in WP Activity Log <= 4.5.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Activity Log the fix is 4.5.2: builds <= 4.5.0 are affected, anything from 4.5.2 onward is not.
Remediation
Update to version 4.5.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Activity Log 4.5.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Activity Log
- 9.8WP Activity Log <= 4.1.4 SQL Injection
- 8.8CVE-2014-5072: WP Activity Log <= 1.2.4 Cross-Site Request Forgery
CVE-2014-5072 - 8.1CVE-2026-54806: WP Activity Log <= 5.6.3.1 PHP Object Injection
CVE-2026-54806 - 7.2CVE-2025-0924: WP Activity Log <= 5.2.2 Stored Cross-Site Scripting
CVE-2025-0924 - 7.2CVE-2024-10793: WP Activity Log <= 5.2.1 Stored Cross-Site Scripting
CVE-2024-10793 - 7.1WP Activity Log 1.5 - 2.4.3 Reflected Cross-Site Scripting
- 6.6CVE-2025-0767: WP Activity Log <= 5.3.2 PHP Object Injection
CVE-2025-0767 - 6.4CVE-2026-56005: WP Activity Log <= 5.6.3.1 Stored Cross-Site Scripting
CVE-2026-56005
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C