CVE-2026-24378
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 · uneditedDeserialization of Untrusted Data vulnerability in Metagauss EventPrime eventprime-event-calendar-management allows Object Injection.This issue affects EventPrime: from n/a through <= 4.2.8.0.
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 · high confidenceThis is a PHP Object Injection vulnerability caused by unsafe deserialization of user-controlled data in the EventPrime event calendar plugin. The deserialization of untrusted data allows attackers to potentially instantiate arbitrary PHP objects, which can lead to remote code execution if certain magic methods (__destruct, __wakeup, etc.) are present in the application or loaded plugins.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm EventPrime plugin installationNavigate to WordPress admin > Plugins and look for 'EventPrime' or check the wp-content/plugins directory for an 'eventprime' folderAffected if EventPrime plugin is not installed on the WordPress site
-
Identify installed EventPrime versionIn WordPress admin > Plugins > EventPrime, view the plugin details to see the version number, or check the main plugin file header for the 'Version' tagAffected if The installed version has not received the security patch for the deserialization vulnerability
-
Verify plugin is activeCheck WordPress admin > Plugins to confirm EventPrime status shows as 'Active'Affected if The plugin is active and processing user-controlled data that could reach deserialization routines
-
Inspect for deserialization usage in plugin codeSearch plugin files for calls to unserialize() function, particularly with user-supplied input from $_POST, $_GET, or $_COOKIEAffected if The plugin contains unserialize() calls handling untrusted data without validation
-
Check for magic methods in plugin or loaded extensionsSearch plugin PHP files for __destruct, __wakeup, __toString, or other magic method definitions that could be chained for RCEAffected if Magic methods exist that could be triggered via object injection to achieve code execution
The environment is affected if EventPrime is installed, active, running an unpatched version, and the vulnerable deserialization code paths are accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade EventPrime to the latest version to receive the patch for this deserialization vulnerability. If immediate patching is not possible, disable or restrict the plugin until the update can be applied, as CVSS 9.8 indicates critical risk.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24378 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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