Stout Google CalendarWordPress extension · Mattmckenny
CVE-2023-45273
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 Matt McKenny Stout Google Calendar plugin <= 1.2.3 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 Matt McKenny Stout Google Calendar WordPress plugin affecting versions 1.2.3 and below. The vulnerability allows attackers to trick authenticated users into unknowingly submitting malicious requests to the affected plugin, potentially performing unauthorized actions.
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
Stout Google CalendarWordPress extension
<= 1.2.3CVSS 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 the plugin versionIn the WordPress admin dashboard, go to Plugins > Installed Plugins. Find 'Mattmckenny Stout Google Calendar' and view the version number listed under the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag.Affected if The installed version is 1.2.3 or lower.
-
Verify the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins. Confirm that 'Mattmckenny Stout Google Calendar' shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if The plugin is installed and active.
-
Identify plugin endpoints and formsExamine the plugin directory (typically at wp-content/plugins/mattmckenny-stout-google-calendar/) for PHP files handling form submissions or admin actions. Look for functions that process user input without verifying nonce tokens or CSRF tokens.Affected if The plugin processes requests without proper CSRF token validation on admin actions or frontend forms.
-
Check authentication requirementsReview the plugin code to determine whether the vulnerable endpoints require authenticated users (such as administrators or editors) to be logged in. CSRF attacks typically target authenticated sessions.Affected if The plugin performs privileged actions (like saving settings or modifying calendar data) for logged-in users without CSRF protection.
You are affected if the Mattmckenny Stout Google Calendar plugin is installed at version 1.2.3 or below and is currently active in your WordPress 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 dataUpdate the plugin to the latest version to obtain the security fix. If no update is available, consider disabling the plugin until a patched version is released.
Fix this in Stout Google Calendar
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45273 — 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-45273 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