Activity Log for WordPress <= 1.2.8 - Missing Authorization to Sensitive Information Exposure via Log File
Strategic Overview
- Status
- Patched in 1.2.9
- Affected Plugin
- Activity Log for WordPress
- Affected Version
<= 1.2.8- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-1671
At a glance
CVE-2026-1671 is a medium-severity Missing Authorization vulnerability in the Activity Log for WordPress WordPress plugin, affecting versions <= 1.2.8. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.2.9; sites on affected versions should update now. Disclosed February 2026, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
The Activity Log for WordPress plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the winter_activity_log_action() function in all versions up to, and including, 1.2.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view potentially sensitive information (e.g., the password of a higher level user, such as an administrator) contained in the exposed log files.
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. A successful exploit has high impact on confidentiality.
CWE-862: Missing Authorization
Activity Log for WordPress <= 1.2.8 carries this weakness at winter_activity_log_action(), and reaching it 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 Activity Log for WordPress the fix is 1.2.9: builds <= 1.2.8 are affected, anything from 1.2.9 onward is not.
Remediation
Update to version 1.2.9, 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: Activity Log for WordPress 1.2.9 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 Activity Log for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C