Plugins · winterlock · data as of 2026-11-04
Is Activity Log for WordPress safe? Known vulnerabilities and latest version
- Latest version
- 1.2.9
- Last updated
- 2026-02-11
- Active installs
- 40+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 6.9.11
Detailed WordPress Activity Log with user request tracking, instant logout, request restrictions, locking, blocking, alerts, and more. — by activity-log.com
What to do
- Update to the latest version (1.2.9). Anything older than 1.2.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get winterlock --field=version shows what you run; wp plugin update winterlock updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.5 CVE-2026-24987 · published 2026-03-25
Missing authorization check in Activity Log for WordPress (1.2.7 and older)
- Affected
- 1.2.7 and older
- Fixed in
- 1.2.8
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in activity-log.com WP System Log winterlock allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP System Log: from n/a through <= 1.2.7.
medium 6.5 CVE-2026-1671 · published 2026-02-12
Missing authorization check in Activity Log for WordPress (1.2.8 and older)
- Affected
- 1.2.8 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
Recent activity
- 2026-02-11 — latest release on wordpress.org (1.2.9).
- 2026-03-25 — Missing authorization check disclosed (CVE-2026-24987), fixed in 1.2.8.
- 2026-02-12 — Missing authorization check disclosed (CVE-2026-1671), fix version not stated.
Get an email when Activity Log for WordPress has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Activity Log for WordPress (winterlock) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by activity-log.com (2 tracked)
Types found in this plugin: Missing authorization (2)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/winterlock (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/winterlock"><img src="https://laskyr.com/plugins/winterlock/badge.svg" alt="Activity Log for WordPress vulnerability status"></a>