dbcve.org
Spiffy CalendarWordPress extension · Spiffyplugins

CVE-2023-49745

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to 4.9.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Spiffy Plugins Spiffy Calendar allows Stored XSS.This issue affects Spiffy Calendar: from n/a through 4.9.5.

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 confidence

Stored Cross-site Scripting (XSS) vulnerability in Spiffy Calendar plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields that gets stored in the database and executed when other users view the affected pages. This is a classic input validation failure where user-supplied data is rendered in web pages without proper output encoding.

MitigationApply output encoding/escaping when rendering user-supplied data in web pages and implement input validation/sanitization at data entry points. Update to the latest patched version if available from the vendor.

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
Spiffy CalendarWordPress extension
Affected:< 4.9.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Spiffy Calendar plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Spiffy Calendar' by Spiffyplugins in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active.
  2. Determine the installed version
    In the Plugins list, click on the plugin name or view its details to find the version number displayed (e.g., 'Version 4.9.5' or 'Version 4.9.0'). Compare this to the affected version 4.9.6.
    Affected if The installed version is below 4.9.6 (e.g., 4.9.5, 4.9.0, or any version number less than 4.9.6).
  3. Identify users with access to create or edit events
    Check WordPress user roles and permissions. Navigate to Users > All Users and review which roles have access to the Spiffy Calendar event creation/edit screens (typically Contributors, Authors, Editors, or Administrators).
    Affected if Any user role other than Administrator can access the calendar event input forms.
  4. Inspect database for suspicious stored scripts
    Access the WordPress database (via phpMyAdmin or CLI) and query the plugin's database tables for any HTML script tags or JavaScript code patterns. Look for entries containing '<script', 'javascript:', or event handler attributes (onerror, onload, etc.) in fields that store calendar event data.
    Affected if Any records in the plugin tables contain encoded or raw JavaScript code that was not intentionally entered by an administrator.
  5. Review event display pages for unencoded output
    Create a test event with a simple marker (e.g., text containing <strong>bold</strong>) and view the calendar page where events are displayed. If HTML renders as bold rather than being displayed as plain text, output encoding is not applied.
    Affected if User-supplied input is rendered as functional HTML or JavaScript when viewed by other users.

A user is affected if the Spiffy Calendar plugin version is below 4.9.6 and any authenticated user can input data that gets rendered without encoding on calendar display pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.9.6 or later
Fixed in 4.9.6
Interim mitigation

Apply output encoding/escaping when rendering user-supplied data in web pages and implement input validation/sanitization at data entry points. Update to the latest patched version if available from the vendor.

Recommended fix High confidence

4.9.6

  1. 1. Create a full backup of the WordPress site before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Spiffy Calendar' in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.9.6 or later
  6. 6. Alternatively, navigate to Dashboard > Updates to see all available updates and update Spiffy Calendar from there
  7. 7. After updating, verify the plugin version shows 4.9.6 or higher
  8. 8. 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 Spiffy Calendar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49745 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49745 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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