dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-39532

HIGH · 8.8 CVSS v3.1 Published 2026-06-15
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
Contributor PHP Object Injection in Events Calendar for GeoDirectory <= 2.3.25 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 · high confidence

This is a PHP Object Injection vulnerability in the Events Calendar for GeoDirectory WordPress plugin affecting versions up to 2.3.25. The flaw allows users with Contributor-level permissions or higher to inject malicious PHP objects through unsanitized input, potentially leading to remote code execution via the plugin's deserialization routines.

MitigationUpdate the Events Calendar for GeoDirectory plugin to the latest version beyond 2.3.25. If an update is unavailable, review user accounts with Contributor-level access and consider implementing additional input sanitization or temporarily disabling the plugin.

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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Events Calendar for GeoDirectory' or check the plugin files in wp-content/plugins/ for a directory matching geodir-event-calendar
    Affected if The plugin is installed and active
  2. Determine the installed version
    Check the plugin header in the main PHP file (typically includes/version.php or the main plugin file) for the version number, or view the plugin in WordPress admin which displays the version
    Affected if The version is 2.3.25 or lower
  3. Check for Contributor-level user accounts
    In WordPress admin, go to Users and review the role column for any accounts with Contributor role or higher (Contributor, Author, Editor, Administrator)
    Affected if There are active users with Contributor-level permissions or higher who have access to the site
  4. Identify if the plugin handles serialized data
    Review plugin settings or look for use of unserialize() calls in plugin code related to event data import or front-end submissions
    Affected if The plugin accepts or processes serialized input from users (this is the vulnerability mechanism)

You are affected if the Events Calendar for GeoDirectory plugin is installed at version 2.3.25 or lower and you have users with Contributor-level access or higher.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Events Calendar for GeoDirectory plugin to the latest version beyond 2.3.25. If an update is unavailable, review user accounts with Contributor-level access and consider implementing additional input sanitization or temporarily disabling the plugin.

Recommended fix Moderate confidence

Events Calendar for GeoDirectory version > 2.3.25 (latest available version)

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the 'Events Calendar for GeoDirectory' plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. After updating, verify the plugin is running on a version higher than 2.3.25.
  6. 6. Test that the Events Calendar functionality works correctly after the update.
Caveat Review the plugin's changelog for any breaking changes between your current version and the new version before upgrading in production environments.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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