Events Calendar*WordPress extension · Wpgeodirectory
CVE-2025-26967
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 Stiofan Events Calendar for GeoDirectory events-for-geodirectory allows Object Injection.This issue affects Events Calendar for GeoDirectory: from n/a through <= 2.3.14.
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 confidenceThis is a PHP Object Injection vulnerability in the Stiofan Events Calendar for GeoDirectory WordPress plugin. The flaw allows deserialization of untrusted data, potentially enabling attackers to instantiate arbitrary PHP objects, trigger magic methods, and achieve remote code execution. The vulnerability affects versions up to and including 2.3.14.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Events Calendar*WordPress extension
< 2.3.15CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check plugin version in WordPressNavigate to Plugins > Installed Plugins in WordPress admin. Locate 'Events Calendar for GeoDirectory' (or Stiofan Events Calendar) and read the version number displayed. Alternatively, check the plugin's main PHP file header for 'Version:' comment.Affected if The installed version is 2.3.14 or lower (any version before 2.3.15).
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm the Events Calendar for GeoDirectory plugin has an 'Active' status.Affected if The plugin is active and running a vulnerable version.
-
Identify vulnerable deserialization codeExamine the plugin source code for calls to unserialize() that process data without prior sanitization. Look in files that handle event data, user submissions, or imported data. Common patterns include unserialize($_POST[...]), unserialize($_GET[...]), or unserialize from database fields that accept user input.Affected if Code contains unserialize() calls processing untrusted input without json_decode or validation.
-
Check data input pathwaysReview how the plugin handles data submitted through forms, REST API endpoints, or imported files. Identify if $_REQUEST, $_POST, $_GET, or database values are passed directly to unserialize().Affected if User-controlled data flows into unserialize() without sanitization.
A user is affected if the Events Calendar for GeoDirectory plugin is active and running version 2.3.14 or lower, with unserialize() processing untrusted input present in the codebase.
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.
dbcve · scoped2.3.15
Upgrade to a patched version of Events Calendar for GeoDirectory that implements safe deserialization (e.g., json_decode) instead of unsafe unserialize() calls, and add proper input validation on any user-controlled data passed to deserialization functions.
Events Calendar for GeoDirectory version 2.3.15
- Update the Events Calendar for GeoDirectory plugin to version 2.3.15 or later through the WordPress plugin management interface
- Verify the update was successfully applied by checking the plugin version number
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Events Calendar*
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26967 — 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-2025-26967 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