dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-56053

HIGH · 8.8 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Subscriber PHP Object Injection in EventPrime <= 4.3.4.1 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A PHP Object Injection vulnerability in the EventPrime WordPress plugin (versions <= 4.3.4.1) allows authenticated users with Subscriber-level privileges to inject malicious PHP objects, potentially leading to remote code execution depending on available classes in the plugin or WordPress environment.

MitigationUpdate EventPrime plugin to a version newer than 4.3.4.1. If an update is unavailable, consider restricting or removing Subscriber user capabilities until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify EventPrime plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'EventPrime' or check the plugin files in /wp-content/plugins/event-prime/ for a version file
    Affected if EventPrime plugin is not installed on the WordPress site
  2. Determine installed EventPrime version
    Check the plugin header in event-prime.php for 'Version:' or look at the plugin details page in WordPress admin under Plugins
    Affected if Version is 4.3.4.1 or lower (any version up to and including 4.3.4.1)
  3. Check for Subscriber-level user accounts
    In WordPress admin, go to Users and look for any accounts with the 'Subscriber' role, or query the wp_usermeta table for user_roles containing 'subscriber'
    Affected if At least one user account with Subscriber role exists on the site
  4. Verify if unauthenticated or low-privilege users can access EventPrime functionality
    Review EventPrime plugin settings under Events > Settings to see if event submission or related features are accessible to Subscriber-role users without additional configuration
    Affected if Subscriber users can access event-related functionality that processes user input

Your site is affected if EventPrime plugin version is 4.3.4.1 or lower AND at least one Subscriber-level user account exists, as this combination allows authenticated PHP object injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update EventPrime plugin to a version newer than 4.3.4.1. If an update is unavailable, consider restricting or removing Subscriber user capabilities until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56053 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data