Spiffy CalendarWordPress extension · Spiffyplugins
CVE-2022-29434
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 · uneditedInsecure Direct Object References (IDOR) vulnerability in Spiffy Plugins Spiffy Calendar <= 4.9.0 at WordPress allows an attacker to edit or delete events.
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 confidenceIDOR vulnerability in Spiffy Calendar plugin for WordPress allows authenticated attackers to edit or delete events they don't own by manipulating event IDs in requests. The plugin fails to properly validate user authorization before allowing modify/delete operations on calendar events.
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
Spiffy CalendarWordPress extension
<= 4.9.0CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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.
-
Verify Spiffy Calendar plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Spiffy Calendar, and check the version number displayed under the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/spiffy-calendar/spiffy-calendar.php or check the version in wp-content/plugins/spiffy-calendar/readme.txtAffected if The installed version is 4.9.0 or lower
-
Confirm plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify that Spiffy Calendar shows as 'Active'Affected if The plugin is active and version is 4.9.0 or lower
-
Check for multiple user roles with event accessGo to the Spiffy Calendar settings or WordPress user roles section. Identify if there are multiple user accounts (contributors, authors, editors, or custom roles) that have permission to create or manage calendar eventsAffected if More than one user role has event creation or management permissions, and the plugin version is 4.9.0 or lower
-
Inspect event edit/delete functionalityAccess the calendar frontend or admin interface, note the event ID in the URL when editing or deleting an event (look for parameters like event_id, action=edit, or action=delete). Attempt to access another user's event ID using the same parameters to see if authorization is checkedAffected if Event IDs can be manipulated in edit/delete requests without the plugin validating ownership, and the plugin version is 4.9.0 or lower
If Spiffy Calendar plugin version 4.9.0 or lower is installed and active with multiple users able to manage events, the IDOR vulnerability is present in the environment.
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 Spiffy Calendar plugin to version 4.9.1 or later. If patching is not possible immediately, implement additional access control checks at the application layer to verify event ownership before allowing edit/delete operations.
Fix this in Spiffy Calendar
Scoped from the published advisory
- 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-2022-29434 — 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-2022-29434 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