LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24954: WordPress WpEvently plugin <= 5.0.8 - Deserialization of untrusted data vulnerability

Deserialization of Untrusted Data vulnerability in magepeopleteam WpEvently mage-eventpress allows Object Injection.This issue affects WpEvently: from n/a through <= 5.0.8.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24954 affects the WordPress WpEvently plugin, also identified as mage-eventpress, through version 5.0.8. It could let a logged-in attacker tamper with how the site processes stored data, potentially affecting confidentiality, integrity, and availability. Treat this as high priority for WordPress sites using this plugin.

Executive priority

High. Prioritize affected public WordPress sites, especially those allowing user registration or multiple low-privilege users. No active exploitation is confirmed in the provided sources, but the impact rating warrants timely validation and remediation planning.

Technical view

The issue is CWE-502: deserialization of untrusted data leading to object injection. The CVSS 3.1 score is 8.8 with network access, low complexity, low privileges required, and no user interaction. Sources identify affected versions as WpEvently/mage-eventpress through 5.0.8.

Likely exposure

Exposure is limited to WordPress installations with magepeopleteam WpEvently, package mage-eventpress, installed at version 5.0.8 or earlier. Sites without this plugin are not indicated as affected by the provided sources.

Exploitation context

The CVE record rates this high impact across confidentiality, integrity, and availability. The CVSS vector requires low privileges, so exploitation is not described as unauthenticated. The provided data does not show CISA KEV listing or confirmed active exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The sources do not provide exploit details, a fixed version, or vendor mitigation text. Avoid assuming unauthenticated exploitability; the published CVSS vector is PR:L.

Mitigation direction

  • Inventory WordPress sites for WpEvently or mage-eventpress plugin usage.
  • Identify plugin versions and prioritize any version 5.0.8 or earlier.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • If no fix is available, consider disabling the plugin where business impact allows.
  • Restrict WordPress account creation and review low-privilege user access.

Validation and detection

  • Confirm whether WpEvently or mage-eventpress is installed on each WordPress site.
  • Record installed plugin version and compare against affected range through 5.0.8.
  • Review plugin advisories for updated affected and fixed version information.
  • Check logs for unusual activity by low-privilege WordPress users.
  • Document compensating controls if the plugin cannot be removed or updated.
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-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-24954 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-24954Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.