dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-23549

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 magepeopleteam WpEvently mage-eventpress allows Object Injection.This issue affects WpEvently: from n/a through <= 5.1.1.

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

The vulnerability is a PHP Object Injection flaw in the WpEvently (mage-eventpress) WordPress plugin. It allows attackers to deserialize untrusted data, potentially leading to remote code execution if a suitable PHP 'gadget chain' exists in the application or other installed plugins.

MitigationImmediately update WpEvently to the latest version if available. If no patch exists, disable and remove the plugin until a fix 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
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 checks

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

  1. Confirm plugin installation
    Navigate to WordPress admin > Plugins and look for 'WpEvently' or 'mage-eventpress' or 'MageEventPress' in the installed plugins list
    Affected if The plugin is installed and active
  2. Identify installed version
    In WordPress admin > Plugins, click on the plugin name to view details, or check the plugin header in wp-content/plugins/mage-eventpress/mage-eventpress.php for the 'Version' comment
    Affected if The version is unknown, unpatched, or older than the fixed release version
  3. Verify deserialization is reachable
    Search the plugin files (especially in includes/ or classes/ directories) for calls to PHP unserialize() function that accept user-controlled input (e.g., $_GET, $_POST, $_REQUEST parameters)
    Affected if The plugin code contains unserialize() calls processing untrusted input without validation
  4. Check for gadget chain dependencies
    Review all installed WordPress plugins for known PHP Object Injection gadget chains (common ones: Popular Gadget, YARPP, Caldera Forms, Gravity Forms, or custom theme code with __wakeup/__set/__get magic methods)
    Affected if Any other installed plugin or theme contains exploitable gadget chain classes that could be triggered via the vulnerable deserialization point

You are affected if WpEvently/mage-eventpress is installed with a vulnerable version that processes untrusted serialized data AND a gadget chain exists somewhere in the WordPress environment.

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

Immediately update WpEvently to the latest version if available. If no patch exists, disable and remove the plugin until a fix is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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