Event CalendarWordPress extension · Total Soft
CVE-2022-38067
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 · uneditedUnauthenticated Event Deletion vulnerability in Totalsoft Event Calendar – Calendar plugin <= 1.4.6 at WordPress.
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 confidenceThe Totalsoft Event Calendar WordPress plugin versions 1.4.6 and below contains an unauthenticated event deletion vulnerability, allowing any unauthenticated user to delete events from the calendar without requiring any authentication credentials or privileges.
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
Event CalendarWordPress extension
<= 1.4.6CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Locate the Total Soft Event Calendar pluginCheck the WordPress plugins directory at wp-content/plugins/ for a folder named 'total-soft-event-calendar' or similar variantAffected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed versionOpen the main plugin file (usually total-soft-event-calendar.php or similar) and locate the version constant or header comment that states the plugin versionAffected if The version declared in the plugin file is 1.4.6 or lower
-
Confirm the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and verify whether Total Soft Event Calendar is activatedAffected if The plugin is active on the WordPress site
-
Verify unauthenticated event deletion is possibleCheck if the plugin's event deletion endpoint (typically involving a request to wp-admin/admin-ajax.php or a front-end ajax handler with an action like 'delete_event' or similar) can be accessed without authenticationAffected if The event deletion functionality is accessible without requiring authentication credentials
The environment is affected if the Total Soft Event Calendar plugin is installed, active, and running version 1.4.6 or lower, allowing unauthenticated users to delete calendar events.
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 dataUpdate the Totalsoft Event Calendar plugin to the latest version immediately. If no patched version is available, disable and remove the plugin until a fix is released.
Fix this in Event Calendar
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38067 — 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-38067 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