dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-13968

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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
The Starboard Suite Reservation Calendars plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shortcode attributes in the [starboard-suite-lightbox] shortcode in all versions up to, and including, 3.1.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 confidence

The Starboard Suite Reservation Calendars WordPress plugin is vulnerable to stored XSS via the [starboard-suite-lightbox] shortcode due to insufficient input sanitization and output escaping of shortcode attributes. Authenticated attackers with Contributor-level access can inject malicious scripts that execute when users view affected pages.

MitigationUpdate the plugin to version 3.1.5 or later; if a patched version is unavailable, remove or disable the shortcode until the vendor releases a fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify the plugin is installed
    Go to WordPress Admin > Plugins and look for 'Starboard Suite Reservation Calendars' in the installed plugins list. Note the version number displayed next to the plugin name.
    Affected if The plugin is installed and active.
  2. Compare installed version to the patched release
    Check the installed version number (from the Plugins page) against version 3.1.5. The plugin version is typically shown below the plugin name on the Plugins > Installed Plugins page.
    Affected if The installed version is lower than 3.1.5 (e.g., 3.1.4, 3.1.3, etc.).
  3. Search for usage of the vulnerable shortcode
    Use WordPress search or a database query to find posts, pages, or custom post types containing the string '[starboard-suite-lightbox]' in the post_content field.
    Affected if The shortcode [starboard-suite-lightbox] is present in any published content.
  4. Review shortcode attribute values in existing content
    Examine any posts/pages containing the shortcode and inspect the attributes used (e.g., any custom parameters passed to the shortcode). Look for unescaped or unvalidated attribute values in the rendered output.
    Affected if The shortcode is present AND the rendered page displays unsanitized attribute values that could contain script tags.

A user is affected if the Starboard Suite Reservation Calendars plugin is installed with a version lower than 3.1.5 AND the [starboard-suite-lightbox] shortcode is used in any content, allowing stored XSS injection via shortcode attributes.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.1.5 or later; if a patched version is unavailable, remove or disable the shortcode until the vendor releases a fix.

Recommended fix Moderate confidence

Version higher than 3.1.4 (check WordPress plugin repository for latest release)

  1. Check the WordPress plugin repository for the Starboard Suite Reservation Calendars plugin
  2. Navigate to Plugins > Add New > Upload or search for Starboard Suite Reservation Calendars
  3. Verify if a version newer than 3.1.4 is available for download
  4. If a newer version exists, update the plugin via WordPress admin or upload the new version
  5. If no newer version is available, consider alternative plugins that provide similar reservation calendar functionality with active security support
  6. Alternatively, contact the plugin developer directly to confirm if a patched version exists or is pending release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13968 — 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-2025-13968 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