LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23549: WordPress WpEvently plugin <= 5.1.1 - PHP Object Injection vulnerability

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-23549 is a critical vulnerability in the WordPress WpEvently / mage-eventpress plugin through version 5.1.1. It involves unsafe handling of serialized data, which can allow PHP object injection. For affected public WordPress sites, the business concern is potential full compromise of confidentiality, integrity, and availability.

Executive priority

Treat this as urgent for any business-critical WordPress site using WpEvently. The severity is critical, exploitation requires no authentication per CVSS, and no confirmed fixed version is present in the provided sources. Immediate inventory and containment decisions are warranted.

Technical view

The CVE describes CWE-502 deserialization of untrusted data in magepeopleteam WpEvently mage-eventpress. CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges, and no user interaction. Public sources identify affected versions as WpEvently through 5.1.1. The provided sources do not name a fixed version.

Likely exposure

Exposure is likely limited to WordPress installations running the WpEvently / mage-eventpress plugin at version 5.1.1 or earlier. Internet-facing WordPress sites are the highest priority to check because the CVSS vector indicates network attackability without authentication.

Exploitation context

The source bundle does not show CISA KEV listing, confirmed active exploitation, or public exploit details. However, the vulnerability class and CVSS vector indicate high exploitation potential if reachable and if a vulnerable plugin version is installed.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The affected range is through 5.1.1, but the bundle’s affected object has sparse version metadata. No exploit status, patch version, or detailed attack preconditions are provided in the supplied public sources.

Mitigation direction

  • Inventory WordPress sites for the WpEvently / mage-eventpress plugin.
  • Prioritize internet-facing sites running version 5.1.1 or earlier.
  • Check the vendor and Patchstack entry for fixed-version guidance.
  • If no fix is available, disable or remove the plugin pending vendor guidance.
  • Apply any vendor-provided update after testing in staging.

Validation and detection

  • Confirm whether mage-eventpress or WpEvently is installed.
  • Record the installed plugin version on each WordPress site.
  • Flag version 5.1.1 or earlier as potentially affected.
  • Verify remediation by confirming the plugin is updated, disabled, or removed.
  • Monitor vendor and vulnerability database updates for changed affected-version 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-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-23549 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-23549Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.