LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24536: WordPress Webpushr plugin <= 4.38.0 - Sensitive Data Exposure vulnerability

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in webpushr Webpushr webpushr-web-push-notifications allows Retrieve Embedded Sensitive Data.This issue affects Webpushr: from n/a through <= 4.38.0.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24536 is a medium-severity information exposure issue in the WordPress Webpushr plugin through version 4.38.0. An unauthenticated remote attacker may be able to retrieve embedded sensitive data. The available sources do not identify active exploitation or a specific fixed version.

Executive priority

Treat this as a moderate-priority WordPress exposure issue. It does not currently show known exploited status, but unauthenticated access and potential sensitive data disclosure justify prompt inventory and remediation planning, especially for public marketing or customer-facing sites.

Technical view

The CVE describes CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere in webpushr-web-push-notifications. CVSS 3.1 is 5.3, with network access, low complexity, no privileges, and no user interaction required. Impact is limited to confidentiality; integrity and availability are not affected in the CVSS vector.

Likely exposure

Exposure is likely limited to WordPress sites running the Webpushr plugin at version 4.38.0 or earlier. Public sources do not provide more detail on the exposed data type, affected endpoint, or environmental prerequisites.

Exploitation context

The CVSS vector indicates unauthenticated network exploitability with low complexity. The source bundle shows this CVE is not in CISA KEV, and no cited source claims active exploitation. Do not treat it as actively exploited based on current evidence.

Researcher notes

Public detail is limited. The record identifies sensitive information exposure but does not describe the vulnerable component, data exposed, proof-of-concept status, or fixed release. Avoid assumptions beyond Webpushr plugin versions through 4.38.0 and the CVSS/CWE data provided.

Mitigation direction

  • Inventory WordPress sites for the Webpushr plugin.
  • Identify installations running Webpushr version 4.38.0 or earlier.
  • Check vendor and Patchstack guidance for fixed versions or workarounds.
  • Disable or remove the plugin where business use is not required.
  • Prioritize remediation for internet-facing WordPress sites.

Validation and detection

  • Confirm plugin name: webpushr-web-push-notifications.
  • Record installed Webpushr versions across WordPress assets.
  • Flag any active installation at version 4.38.0 or earlier.
  • Review public vendor or Patchstack pages for updated remediation status.
  • Monitor web logs for unusual unauthenticated requests to plugin-related paths.
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 · low confidence lookup

CWE-497: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-24536 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
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
webpushrWebpushrwebpushr-web-push-notifications, 0unaffected
Weakness

CWE details

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

CWE-497 · source CWE mapping

Exposure of Sensitive System Information to an Unauthorized Control Sphere

Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.