Simple CalendarWordPress extension · Xtendify
CVE-2023-46189
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Simple Calendar – Google Calendar Plugin <= 3.2.5 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Simple Calendar WordPress plugin (Google Calendar integration) affecting versions 3.2.5 and below. The vulnerability allows attackers to execute unauthorized state-changing actions on behalf of authenticated users by tricking them into visiting malicious pages.
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
Simple CalendarWordPress extension
< 3.2.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Simple Calendar plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Simple Calendar. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header or version.php for the version constant.Affected if Version is 3.2.5 or below, or if the version field cannot be confirmed as 3.2.6 or higher
-
Verify plugin is activeCheck if the Simple Calendar plugin is currently activated in WordPress under Plugins > Installed Plugins. Look for 'Active' status indicator.Affected if Plugin is active and version cannot be verified as 3.2.6 or higher
-
Check plugin files for version definitionAccess site files via FTP or file manager. Navigate to /wp-content/plugins/simple-calendar/ and open the main plugin file (usually simple-calendar.php or similar) to read the Version header comment.Affected if Version defined in plugin header is 3.2.5 or below
-
Confirm Google Calendar feed is configuredNavigate to Simple Calendar > Settings > Feeds in WordPress admin. Check if any Google Calendar feeds are created and saved.Affected if Google Calendar feeds exist and plugin version is below 3.2.6
If Simple Calendar plugin version is below 3.2.6 and the plugin is active, the site is vulnerable to CSRF attacks via the plugin's state-changing operations.
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 · scoped3.2.6
Update the Simple Calendar plugin to the latest version beyond 3.2.5. If no update is available, implement anti-CSRF tokens (nonces) on all form submissions and state-changing operations within the plugin.
Simple Calendar 3.2.6
- Upgrade Simple Calendar plugin to version 3.2.6 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Simple Calendar
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46189 — 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-2023-46189 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