dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1671

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Activity Log for WordPress plugin has a broken access control vulnerability in the winter_activity_log_action() function. The function lacks capability checks, allowing authenticated users with Subscriber-level permissions (the lowest privilege role) to access sensitive log data including administrator passwords. This is an Insecure Direct Object Reference (IDOR) combined with broken access control.

MitigationUpdate to version 1.2.9 or later which includes proper capability checks. Until patched, audit subscriber-level accounts and consider disabling the plugin or restricting user registration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Activity Log plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Activity Log' or 'WP Activity Log' plugin. Note the installed version displayed.
    Affected if Plugin is installed and version is earlier than 1.2.9
  2. Confirm plugin version is vulnerable
    Compare the installed version to the fixed version 1.2.9. Check the plugin's main file header or the plugins page version column.
    Affected if Installed version is lower than 1.2.9
  3. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the Role column. Count or note any users assigned the Subscriber role.
    Affected if Any user account with Subscriber role exists in the system
  4. Verify the vulnerable function exists
    Access the plugin files via file manager or FTP. Locate the main plugin file and search for the function winter_activity_log_action(). The presence of this function without capability checks indicates the vulnerability.
    Affected if The function winter_activity_log_action() exists without proper capability checks (verified via code review or behavior)
  5. Test the IDOR vulnerability directly if safe to do so
    Using a test subscriber account, attempt to access the activity log endpoint that calls winter_activity_log_action(). Observe whether sensitive data such as administrator passwords or other users' credentials are exposed in the response.
    Affected if Subscriber-level account can retrieve sensitive log data or administrator credentials

A user is affected if the Activity Log plugin is installed with a version lower than 1.2.9 and at least one subscriber-level user account exists in the WordPress installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.2.9 or later which includes proper capability checks. Until patched, audit subscriber-level accounts and consider disabling the plugin or restricting user registration.

Recommended fix Moderate confidence

latest version available in WordPress plugin repository (version > 1.2.8)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the 'Activity Log for WordPress' plugin in the list
  3. 3. If an update is available, click 'Update Now' to install the latest version
  4. 4. Alternatively, download the latest version from the official WordPress plugin repository at wordpress.org/plugins/activity-log/
  5. 5. After updating, verify the plugin version is greater than 1.2.8

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1671 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1671 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data