Skip to main content

EventPrime EUVDEUVD-2026-39382

| CVE-2026-56053 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-06-25 Patchstack GHSA-h5wm-8hx6-m9ff
8.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Subscriber account via registration
  2. Delivery
    Send crafted serialized object to plugin endpoint
  3. Exploit
    Trigger PHP object injection via unserialize
  4. Execution
    Invoke POP gadget chain in loaded classes
  5. Impact
    Achieve code execution or data tampering

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a valid authenticated Subscriber-level account on the target WordPress site (CVSS PR:L) - exploitation is network-based with low complexity and no user interaction (AV:N/AC:L/UI:N). The practical limiting factors are: (1) the attacker must obtain Subscriber access, which is trivial on sites with open registration but a real barrier where registration is closed; and (2) successful escalation to code execution depends on an exploitable PHP POP gadget chain being present in WordPress core or other installed plugins - without a usable chain, impact may be limited to lower-severity object instantiation effects. Affected only on EventPrime versions <= 4.3.4.1.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 8.8 High) indicates network-reachable, low-complexity exploitation requiring only low privileges and no user interaction, with high impact across confidentiality, integrity, and availability - consistent with object-injection bugs that can yield RCE. The key limiter is PR:L: the attacker must already hold a valid Subscriber-level account, so on sites where open self-registration is disabled the realistic attack surface narrows considerably; on sites allowing public registration (common for WordPress), this is effectively a near-unauthenticated path. No EPSS score, KEV listing, POC, or SSVC decision data was provided in the input, so probability-of-exploitation and automatability cannot be quantified here - the priority rests on the high CVSS and the well-understood severity of deserialization flaws rather than on confirmed exploitation signals. The CVSS C:H/I:H/A:H rating assumes a usable gadget chain exists; actual impact on a given deployment may be lower if no exploitable chain is loaded - this should be verified against the specific WordPress environment.

Exploit ScenarioDerived

An attacker registers (or compromises) a Subscriber account on a WordPress site running EventPrime <= 4.3.4.1, then submits a crafted request containing a malicious serialized PHP object to a vulnerable plugin endpoint. When the plugin deserializes the input, an available gadget chain is triggered, potentially allowing the attacker to read sensitive data, alter site content, or execute code. No public proof-of-concept was identified in the provided data; exploitation is network-based with low complexity per the CVSS vector.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 25, 2026

PHP Object Injection in the EventPrime event-calendar-management WordPress plugin (versions 4.3.4.1 and earlier) allows an authenticated attacker holding only a low-privilege Subscriber account to inject crafted serialized objects into an unsafe deserialization sink. Depending on the PHP gadget chains present in WordPress core, the plugin, or other installed plugins, this can escalate to data tampering, information disclosure, or remote code execution. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; it was reported by Patchstack.

RemediationAI

Upgrade EventPrime to the latest available release above 4.3.4.1; the input data does not specify the exact patched version, so confirm the fixed build directly via the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/eventprime-event-calendar-management/vulnerability/wordpress-eventprime-plugin-4-3-4-1-php-object-injection-vulnerability) and the plugin's WordPress.org changelog before deploying. Until patched, reduce the attack surface by disabling open user self-registration (Settings > General > 'Anyone can register') so attackers cannot trivially obtain the Subscriber account the exploit requires - trade-off: this blocks legitimate public sign-ups. Additionally, restrict or audit existing low-privilege accounts, and deploy a WordPress WAF (such as Patchstack's own virtual patching) to filter serialized-object payloads to plugin endpoints - trade-off: WAF rules may need tuning to avoid false positives. No vendor-released patch version is independently confirmed from the available data, so treat virtual patching as interim, not a substitute for upgrading.

Affected VersionsENISA

EventPrime n/a ≤4.3.4.1

Affected Packages

euvd eventprime no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is classified as CWE-502 (Deserialization of Untrusted Data). EventPrime is a PHP-based WordPress plugin for event and calendar management. The flaw arises when attacker-controllable input reaches a PHP unserialize()-style operation without validation, letting an attacker instantiate arbitrary PHP objects. PHP Object Injection is rarely directly exploitable on its own - its real impact depends on the availability of 'POP gadget' chains (classes with exploitable __wakeup(), __destruct(), or other magic methods) loaded in the WordPress runtime, which is why such bugs are often chained with code in core or third-party plugins to reach file write, SQL, or code execution. The single CPE provided (cpe:2.3:a:eventprime:eventprime:*) confirms the affected component is the EventPrime application itself across all versions up to and including 4.3.4.1.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable with low complexity and no interaction; requires a Subscriber account (PR:L); object injection can yield full C/I/A impact via gadget chains, scope unchanged.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Subscriber PHP Object Injection in EventPrime <= 4.3.4.1 versions.

Executive ViewAI

Why It Matters

EventPrime WordPress plugin (versions ≤4.3.4.1) contains an object injection vulnerability enabling authenticated Subscriber users to manipulate data or potentially execute code, with no public exploit identified at time of analysis. Any organization using EventPrime where basic user accounts are issued faces system compromise risk to event management systems and data. No patch is currently available, requiring immediate containment of low-privilege account access.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict or suspend Subscriber account creation; disable plugin if non-essential to operations; monitor access logs for exploitation attempts; limit WordPress access to trusted administrators only; consider temporary plugin removal pending vendor patch release.

Threat Intelligence Overview

EPSS Score
0.4%
Top 69% exploitable
Prevalence
Medium
moderately popular WordPress event-calendar plugin, common but not universal
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy