LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32354: WordPress WpEvently plugin < 5.1.9 - Sensitive Data Exposure vulnerability

Insertion of Sensitive Information Into Sent Data vulnerability in magepeopleteam WpEvently mage-eventpress allows Retrieve Embedded Sensitive Data.This issue affects WpEvently: from n/a through < 5.1.9.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32354 is a medium-severity data exposure issue in the WordPress WpEvently plugin, package mage-eventpress. Affected versions before 5.1.9 may include sensitive information in data sent to users. The main business risk is unintended disclosure, not system takeover or outage based on the published CVSS details.

Executive priority

Treat as a timely patching and exposure-review item, especially for public WordPress sites handling customer or event data. It is not described as ransomware-enabling or actively exploited in the provided sources, but unauthenticated data exposure can still create privacy, reputational, and compliance concerns.

Technical view

The CVE describes CWE-201, insertion of sensitive information into sent data, affecting magepeopleteam WpEvently through versions below 5.1.9. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, and no integrity or availability impact.

Likely exposure

Internet-facing WordPress sites using the WpEvently / mage-eventpress plugin below 5.1.9 are the likely exposure group. Sites not using this plugin, or running unaffected versions, are not indicated as exposed by the provided sources.

Exploitation context

The CVSS vector indicates unauthenticated remote exposure is possible, but the sources do not state active exploitation. The CVE is not listed as KEV in the provided bundle. No exploit details are provided in the cited material.

Researcher notes

The available record is sparse. It identifies the weakness class, affected plugin, version boundary, and CVSS vector, but does not describe the specific data exposed or affected endpoint. Avoid assumptions about exploitability beyond the CVSS and cited description.

Mitigation direction

  • Inventory WordPress sites for the WpEvently / mage-eventpress plugin.
  • Upgrade WpEvently to 5.1.9 or later if available from trusted sources.
  • If upgrade status is unclear, check vendor or Patchstack guidance before accepting risk.
  • Reduce public exposure of affected functionality where business operations allow.
  • Review exposed content for sensitive information that should not be sent.

Validation and detection

  • Confirm whether mage-eventpress is installed on each WordPress site.
  • Record the installed WpEvently version and compare it against 5.1.9.
  • Review public pages or responses for unintended embedded sensitive data.
  • Check security monitoring for unusual access to affected plugin functionality.
  • Document remediation status for all sites running versions below 5.1.9.
Prepared
Confidence
high
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-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-32354 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-32354Attack 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
magepeopleteamWpEventlymage-eventpress, 0unaffected
Weakness

CWE details

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

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.