LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25389: WordPress EventPrime plugin <= 4.2.8.3 - Sensitive Data Exposure vulnerability

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Metagauss EventPrime eventprime-event-calendar-management allows Retrieve Embedded Sensitive Data.This issue affects EventPrime: from n/a through <= 4.2.8.3.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25389 is a medium-severity information exposure issue in the WordPress EventPrime plugin through version 4.2.8.3. An unauthenticated remote attacker may be able to retrieve embedded sensitive data. The available sources do not name the exposed data type or confirm active exploitation.

Executive priority

Treat as a routine but timely WordPress plugin exposure issue. Prioritize internet-facing sites and sites handling sensitive event, user, or business data. Business urgency is moderate because exploitation appears low-complexity, but the known impact is limited to confidentiality and no active exploitation is cited.

Technical view

The CVE describes CWE-497, Exposure of Sensitive System Information to an Unauthorized Control Sphere, in Metagauss EventPrime eventprime-event-calendar-management. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, low confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is most relevant to public WordPress sites running EventPrime through version 4.2.8.3. Sites not using this plugin are not affected based on the provided sources. The affected-version metadata is limited, so plugin inventory should be verified directly.

Exploitation context

The CVSS vector indicates unauthenticated remote access may be sufficient. The source bundle does not provide exploit details, proof-of-concept status, or evidence of active exploitation. This CVE is not marked as CISA KEV in the provided data.

Researcher notes

Public details are sparse. The bundle identifies the vulnerability class and affected range but not the exact data exposed, endpoint behavior, or fixed version. Avoid assuming impact beyond low confidentiality until vendor or Patchstack details provide more evidence.

Mitigation direction

  • Identify WordPress sites using the EventPrime plugin.
  • Check whether EventPrime is version 4.2.8.3 or earlier.
  • Review the vendor or Patchstack advisory for fixed-version guidance.
  • Update or disable the plugin if vendor guidance recommends it.
  • Restrict unnecessary public exposure of event-related endpoints where operationally feasible.

Validation and detection

  • Confirm installed EventPrime versions across WordPress assets.
  • Check plugin inventory against the CVE affected range.
  • Review web logs for unusual unauthenticated access to EventPrime functionality.
  • Monitor vendor, CVE, and Patchstack pages for updated remediation details.
  • Document whether the plugin is unused, updated, disabled, or accepted risk.
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-25389 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-25389Attack 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
MetagaussEventPrimeeventprime-event-calendar-management, 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.