LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24616: WordPress WP Popups plugin <= 2.2.0.5 - Broken Access Control vulnerability

Missing Authorization vulnerability in Damian WP Popups wp-popups-lite allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Popups: from n/a through <= 2.2.0.5.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24616 affects the WordPress WP Popups plugin, package wp-popups-lite. A logged-in user may be able to access data or functionality they should not. The reported impact is mainly confidentiality, not site takeover or disruption. Public sources do not show active exploitation.

Executive priority

Treat as a near-term WordPress plugin hygiene issue, not an emergency based on current evidence. Prioritize internet-facing sites with public registration or many low-privileged users. Remediate during the next maintenance window unless additional exploitation evidence appears.

Technical view

The issue is a missing authorization vulnerability, CWE-862, in Damian WP Popups wp-popups-lite through version 2.2.0.5. CVSS 3.1 is 6.5 with network access, low complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.

Likely exposure

Exposure is most likely on WordPress sites running WP Popups/wp-popups-lite at or below 2.2.0.5, especially where untrusted users can authenticate. Sites without the plugin, or running unaffected versions, are not indicated as exposed by the provided sources.

Exploitation context

CISA KEV is false, and the provided sources do not report active exploitation. The CVSS vector indicates exploitation would require a low-privileged authenticated user and no victim interaction. No public exploit details are included in the source bundle.

Researcher notes

Public metadata is limited. The CVE description says affected through 2.2.0.5, while the Patchstack URL title references 2.2.0.3. Use the CVE affected range unless vendor guidance clarifies. No exploit mechanics, endpoint names, or fixed version are provided in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the WP Popups/wp-popups-lite plugin.
  • Identify installed plugin versions and flag versions at or below 2.2.0.5.
  • Check vendor, WordPress, or Patchstack guidance for a fixed version or official mitigation.
  • Update the plugin if a fixed release is available from trusted sources.
  • Disable or remove the plugin where it is not required.
  • Limit low-privileged account creation on affected sites until remediated.

Validation and detection

  • Confirm whether WP Popups/wp-popups-lite is installed on each WordPress site.
  • Record the exact installed plugin version.
  • Compare installed versions against the affected range through 2.2.0.5.
  • Review user registration and subscriber access exposure on affected sites.
  • Monitor vendor and vulnerability database entries for updated remediation details.
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-24616 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-24616Attack 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
DamianWP Popupswp-popups-lite, 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.