Starboard Suite Reservation Calendars <= 3.1.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes
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.
Quick answer
Starboard Suite Reservation Calendars should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-3.1.4
Fixed versions
- 3.1.5
How to fix it
Starboard Suite Reservation Calendars is affected by CVE-2025-13968, a cross-site scripting issue in versions up to 3.1.4. Wordfence lists the official remediation as updating to version 3.1.5, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, Elementor/page-builder surfaces, reservation or booking workflows, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has Starboard Suite Reservation Calendars installed, including production, staging, multisite, client, WooCommerce, marketplace, and booking environments.
- Confirm the installed Starboard Suite Reservation Calendars version and compare it with the affected range from the Wordfence advisory.
- Update Starboard Suite Reservation Calendars to version 3.1.5, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable Starboard Suite Reservation Calendars or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review user-generated content, forms, widgets, saved plugin settings, comments, profiles, templates, page-builder output, and WooCommerce marketplace/vendor pages for injected scripts or unexpected HTML.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running Starboard Suite Reservation Calendars version is version 3.1.5 or newer, and record the patched version in the remediation ticket.
- Verify the affected fields, widgets, forms, profile data, marketplace pages, or settings now sanitize input and escape output instead of rendering executable scripts.
- Review web server, WordPress, security plugin, WAF, database, WooCommerce, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, vendor, editor, administrator, checkout, form, API, booking, reservation, invoice, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2025-13968?
Starboard Suite Reservation Calendars versions listed as affected should be reviewed: *-3.1.4.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.