CVE-2026-5767
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 · uneditedThe SlideShowPro SC plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `slideShowProSC` shortcode in all versions up to, and including, 1.0.2 due to insufficient input sanitization and output escaping on user supplied attributes. 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 confidenceThe SlideShowPro SC WordPress plugin has a stored XSS vulnerability in its slideShowProSC shortcode due to insufficient input sanitization and output escaping on user-supplied attributes, allowing authenticated attackers with contributor-level access to inject malicious scripts that execute when users access affected pages.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SlideShowPro SC plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate SlideShowPro SC. Note whether it is installed and activated.Affected if Plugin is present and active in the WordPress installation
-
Identify installed plugin versionClick on the plugin from the Plugins list to view version details, or check the plugin header comment in the main PHP file typically located at /wp-content/plugins/slideshowpro-sc/ or similar path.Affected if Version is unpatched or cannot be determined compared to a secure release
-
Find pages using the vulnerable shortcodeSearch the WordPress database via phpmyadmin or WP CLI for posts containing '[slideShowProSC' or '[slideshowpro_sc' shortcode, or use a plugin to scan for shortcode usage.Affected if The shortcode is present in any post, page, or custom post type content
-
Inspect shortcode handler for sanitizationLocate the shortcode handler function in the plugin file (search for add_shortcode('slideShowProSC')) and verify that user-supplied attributes are processed with sanitization functions like sanitize_text_field and escaped with functions like esc_attr or esc_html before output.Affected if Shortcode handler lacks proper sanitization and escaping on attribute values
Environment is affected if the SlideShowPro SC plugin is active, uses the slideShowProSC shortcode, and the shortcode handler does not properly sanitize input or escape output.
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 dataApply proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) to all user-supplied attributes in the shortcode handler, or update to a patched version when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5767 — 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-2026-5767 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