Simple CalendarWordPress extension · Sureswiftcapital
CVE-2023-49151
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Simple Calendar Simple Calendar – Google Calendar Plugin allows Stored XSS.This issue affects Simple Calendar – Google Calendar Plugin: from n/a through 3.2.6.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in the Simple Calendar WordPress plugin (Google Calendar integration) allows authenticated attackers to inject malicious JavaScript through calendar event data that gets rendered without proper sanitization, affecting versions through 3.2.6.
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.8CVSS 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.
-
Confirm Simple Calendar plugin is installedIn WordPress admin, go to Plugins and locate Simple Calendar in the installed plugins listAffected if Plugin is not installed - not affected
-
Check the installed plugin versionIn WordPress admin > Plugins > Simple Calendar, click on the plugin to view version details, or read the version header from the main plugin file in wp-content/plugins/simple-calendar/Affected if Version is 3.2.8 or higher - not affected; version is below 3.2.8 - potentially affected
-
Verify Google Calendar feed is configuredNavigate to Simple Calendar > Calendars and check if any calendar uses Google Calendar as the feed source (Settings > Feed Type shows Google Calendar)Affected if No Google Calendar feeds are configured - lower risk, but version check still applies
-
Inspect rendered calendar output for unescaped HTMLView a published calendar page in a browser, right-click > View Page Source, and look for raw HTML tags or script fragments in event titles or descriptions that should have been encodedAffected if Raw HTML or script tags appear in rendered event data - confirmed vulnerable and affected
Affected if Simple Calendar version is below 3.2.8 AND Google Calendar feeds are configured and displaying events with unsanitized content
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.8
Upgrade to Simple Calendar version 3.2.7 or later which implements proper input sanitization and output encoding to neutralize the XSS vector.
Simple Calendar version 3.2.8 or later
- 1. Backup your WordPress site before making any changes.
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
- 3. Find Simple Calendar in the plugin list.
- 4. Click 'Update Now' if an update is available, or download version 3.2.8 or later from the WordPress plugin repository.
- 5. Verify the plugin is updated to version 3.2.8 or higher.
- 6. Test the calendar functionality to ensure the update did not break existing features.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Simple Calendar
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49151 — 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-49151 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