LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24987: WordPress WP System Log plugin <= 1.2.7 - Broken Access Control vulnerability

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24987 is a broken access control issue in the WordPress WP System Log plugin, affecting versions through 1.2.7. A logged-in user may be able to access sensitive system log information they should not see. The main business risk is confidentiality exposure, not site takeover based on the provided CVSS data.

Executive priority

Treat as a near-term WordPress hygiene issue, especially on sites with many contributors, customers, or contractors. Prioritize systems where logs may contain secrets, personal data, operational details, or security events. It is not currently supported as an emergency active-exploitation item by the provided sources.

Technical view

The issue is CWE-862 Missing Authorization in activity-log.com WP System Log, package name winterlock. CVSS 3.1 is 6.5: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity or availability impact. Sources identify affected versions as through 1.2.7.

Likely exposure

Exposure is likely limited to WordPress sites that have WP System Log installed at version 1.2.7 or earlier and allow untrusted or lower-privileged authenticated users. Public unauthenticated exposure is not indicated by the CVSS vector.

Exploitation context

The CVE record does not indicate CISA KEV listing, and the provided sources do not state active exploitation. Exploitation requires some authenticated access. The likely target would be unauthorized viewing of sensitive system log data, depending on what the plugin records.

Researcher notes

Evidence is limited to the CVE data and Patchstack VDB reference. No exploit details, fixed version, or active exploitation evidence are included in the provided bundle. The CVSS vector is important: PR:L and C:H indicate authenticated confidentiality exposure is the central concern.

Mitigation direction

  • Inventory WordPress sites for the WP System Log plugin.
  • Identify installations running version 1.2.7 or earlier.
  • Check vendor or Patchstack guidance for a fixed version or official workaround.
  • Update the plugin if a fixed release is available from trusted sources.
  • Disable the plugin where it is not operationally required.
  • Restrict WordPress accounts to trusted users until remediation is complete.

Validation and detection

  • Confirm the plugin name and installed version on each WordPress site.
  • Review user roles with login access to affected sites.
  • Verify whether sensitive data is present in plugin logs.
  • After remediation, confirm lower-privileged users cannot access restricted log functions.
  • Monitor WordPress and web logs for unusual access to plugin log pages.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24987 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-24987Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
activity-log.comWP System Logwinterlock, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.