LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54742: WordPress WpEvently Plugin <= 4.4.8 - 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 <= 4.4.8.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

WpEvently for WordPress has a high-severity unsafe deserialization flaw through version 4.4.8. An authenticated low-privileged attacker could potentially turn submitted data into unintended PHP objects, leading to serious site compromise if exploitable code paths and gadget chains exist.

Executive priority

Prioritize within the normal high-severity WordPress plugin remediation queue. Escalate for sites that are internet-facing, event-critical, or allow public account registration, because compromise could affect site data, content integrity, and availability.

Technical view

CVE-2025-54742 is CWE-502 deserialization of untrusted data in magepeopleteam WpEvently, package mage-eventpress. The CVSS 3.1 score is 8.8 with network access, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Internet-facing WordPress sites running WpEvently through version 4.4.8 are the relevant exposure. Practical risk is higher where untrusted users can obtain low-privileged WordPress accounts.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. The CVSS vector indicates network-reachable exploitation requiring low privileges and no user interaction. No exploit details or indicators are provided in the source bundle.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. The bundle names object injection from unsafe deserialization but does not provide a fixed version, affected code path, prerequisites beyond CVSS PR:L, exploit indicators, or confirmed exploitation.

Mitigation direction

  • Inventory WordPress sites for WpEvently or mage-eventpress installations.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed version.
  • Update immediately if a vendor-confirmed patched release is available.
  • Disable or remove WpEvently where it is not business-critical.
  • Limit creation and use of low-privileged WordPress accounts.

Validation and detection

  • Confirm each WordPress site's WpEvently plugin version.
  • Treat active versions through 4.4.8 as vulnerable until remediated.
  • Verify the plugin is updated, disabled, or removed after mitigation.
  • Review whether public registration or low-privileged access is enabled.
  • Document any vendor guidance gaps or unavailable patch information.
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-2025-54742 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-2025-54742Attack 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.

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.