LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24376: WordPress WPVulnerability plugin <= 4.2.1 - Broken Access Control vulnerability

Missing Authorization vulnerability in Javier Casares WPVulnerability wpvulnerability allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPVulnerability: from n/a through <= 4.2.1.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24376 is a broken access control issue in the WordPress WPVulnerability plugin through version 4.2.1. A logged-in user may be able to access sensitive information they should not see. The published CVSS score is 6.5, and there is no cited evidence of active exploitation.

Executive priority

Treat this as a near-term WordPress hygiene issue, not a confirmed emergency. Prioritize sites with public registration, many contributors, or sensitive vulnerability-management data. If affected versions are found, update or disable based on vendor guidance.

Technical view

The CVE describes CWE-862 Missing Authorization in Javier Casares WPVulnerability. The CVSS vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning network-reachable exploitation by an authenticated low-privilege user with high confidentiality impact and no stated integrity or availability impact.

Likely exposure

Exposure is limited to WordPress sites running the WPVulnerability plugin at version 4.2.1 or earlier. The CVE data indicates authentication is required, so risk is higher on sites with many user accounts, open registration, compromised accounts, or weak account governance.

Exploitation context

No KEV listing is provided, and the supplied sources do not state active exploitation. The vulnerability appears practical where an attacker already has a low-privilege WordPress account. Public details in the bundle do not identify the exact restricted data or endpoint involved.

Researcher notes

The source bundle identifies the weakness class, affected plugin, version range, and CVSS vector, but does not provide a fixed version, endpoint, proof of concept, or exploitation evidence. Avoid assuming exploitability beyond authenticated broken access control until vendor details are available.

Mitigation direction

  • Inventory WordPress sites for the WPVulnerability plugin and its installed version.
  • If version is 4.2.1 or earlier, check vendor and Patchstack guidance immediately.
  • Update if a vendor-fixed version is available from trusted WordPress channels.
  • Disable or remove the plugin where it is not operationally required.
  • Limit WordPress user accounts and remove unnecessary low-privilege access.

Validation and detection

  • Confirm whether WPVulnerability is installed and active on each WordPress site.
  • Record the plugin version and compare it to the affected range through 4.2.1.
  • Review WordPress user roles for unnecessary or stale accounts.
  • Monitor vendor, CVE, and Patchstack pages for fixed-version details.
  • Check access logs for unusual authenticated activity if the plugin was exposed.
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-24376 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-24376Attack 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
Javier CasaresWPVulnerabilitywpvulnerability, 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.