dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-68047

HIGH · 8.8 CVSS v3.1 Published 2026-01-22
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

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
Deserialization of Untrusted Data vulnerability in Arraytics Eventin wp-event-solution allows Object Injection.This issue affects Eventin: from n/a through <= 4.1.3.

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

This is a PHP Object Injection vulnerability in the Eventin WordPress plugin. The plugin deserializes untrusted data without proper validation, allowing attackers to inject malicious PHP objects. If the plugin or other installed plugins contain POP (Property-Oriented Programming) chains with magic methods (like __destruct or __wakeup), attackers can achieve arbitrary code execution.

MitigationReplace unsafe unserialize() calls with safer alternatives like json_decode(), and implement strict allowlist validation on any deserialized data. Consider using a webhook-based approach or removing the deserialization entirely if possible.

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 Eventin plugin is installed
    Navigate to WordPress admin > Plugins and confirm the Eventin plugin appears in the list of installed plugins
    Affected if Eventin plugin is present in the WordPress installation
  2. Identify installed Eventin version
    In WordPress admin > Plugins, click on the Eventin plugin to view its version number, or inspect the plugin header in wp-content/plugins/eventin/plugin.php for the Version field
    Affected if Version is within the range of affected versions (compare your version to the CVE-advisory-published vulnerable version)
  3. Locate unsafe deserialization calls
    Inspect Eventin plugin source code for unserialize() function calls, particularly in AJAX handlers, REST API endpoints, or frontend submission forms
    Affected if The plugin contains unserialize() calls that process untrusted user input
  4. Check for POP chain gadgets in other plugins
    Review all other installed WordPress plugins for classes with magic methods (__destruct, __wakeup, __toString, __call) that could form a Property-Oriented Programming chain
    Affected if Any installed plugin contains exploitable POP chain gadgets alongside vulnerable Eventin deserialization
  5. Identify data entry points
    Review the WordPress site for public-facing forms, webhooks, or API endpoints that feed data to Eventin processing logic
    Affected if Untrusted serialized data can be submitted through accessible endpoints

A user is affected if the Eventin plugin is installed with a vulnerable version that uses unsafe unserialize() on user-supplied data and POP chain gadgets exist in the plugin ecosystem.

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

Replace unsafe unserialize() calls with safer alternatives like json_decode(), and implement strict allowlist validation on any deserialized data. Consider using a webhook-based approach or removing the deserialization entirely if possible.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68047 — 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-2025-68047 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