Event CalendarWordPress extension · Total Soft
CVE-2022-36390
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 · uneditedAuthenticated (subscriber+) Reflected Cross-Site Scripting (XSS) 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 confidenceAuthenticated (subscriber+) reflected cross-site scripting (XSS) vulnerability in Totalsoft Event Calendar plugin for WordPress versions 1.4.6 and below allows attackers with at least subscriber-level account access to inject malicious JavaScript through unsanitized input parameters.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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.
-
Check if Total Soft Event Calendar plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Total Soft Event Calendar' or check the plugin files in wp-content/plugins/ for a folder containing 'event-calendar' or 'total-soft'Affected if Plugin is not installed or not present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin_plugins page, find Total Soft Event Calendar and note the version number displayed under the plugin name, or read the main plugin PHP file header for 'Version:' fieldAffected if Version is 1.4.6 or lower (any version <= 1.4.6)
-
Check for subscriber-level user accountsIn WordPress admin, go to Users > All Users and review the Role column for any accounts with 'Subscriber' role, or query the wp_usermeta table for user_id values where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'Affected if At least one user account with subscriber-level access exists in WordPress
User is affected if Total Soft Event Calendar plugin version is 1.4.6 or lower AND at least one subscriber-level user account exists in the WordPress installation, allowing the authenticated XSS attack vector to be exploitable.
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 · scopedUpdate Totalsoft Event Calendar plugin to version 1.4.7 or later which contains the patch for this XSS vulnerability.
Totalsoft Event Calendar – Calendar version 1.4.7 or later
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Totalsoft Event Calendar – Calendar' plugin
- Check if an update is available and update to the latest version (version > 1.4.6)
- Verify the update was successful and the plugin is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Event Calendar
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36390 — 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-36390 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