Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4076

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-22

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

Official description

NVD · unedited

The Slider Bootstrap Carousel plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'category' and 'template' shortcode attributes in all versions up to and including 1.0.7. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. The plugin uses extract() on shortcode_atts() to parse attributes, then directly outputs the $category variable into multiple HTML attributes (id, data-target, href) on lines 38, 47, 109, and 113 without applying esc_attr(). Similarly, the $template attribute flows into a class attribute on line 93 without 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

dbcve analysis · high confidence

The Slider Bootstrap Carousel WordPress plugin fails to sanitize and escape the 'category' and 'template' shortcode attributes before outputting them into HTML attributes (id, data-target, href, class). An authenticated attacker with Contributor-level access can inject malicious JavaScript via these attributes that executes when users view the affected pages.

MitigationUpdate to a patched version that properly escapes shortcode attributes using esc_attr() before output. Until patched, audit existing content for malicious shortcodes and consider restricting shortcode usage permissions.

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

CVSS breakdown

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?

dbcve checks

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

Confirm Slider Bootstrap Carousel plugin is installed

Go to WordPress admin > Plugins and look for 'Slider Bootstrap Carousel' in the installed plugins list

Affected if Plugin is not installed on the WordPress site
Identify the installed plugin version

Click on the plugin in the WordPress plugins list to view details, or check the plugin files for a version number in the main PHP file header

Affected if Unable to determine version OR version is unknown/older than patched release
Search for shortcode usage in content

Use WordPress search or a database query to find posts/pages containing the shortcode '[slider_bootstrap_carousel' or similar shortcode tags the plugin registers

Affected if Shortcode is present in any published content
Inspect shortcode attribute values in database

Examine the stored shortcode in posts table (wp_posts) or via plugin editor to check if 'category' or 'template' attributes contain unsanitized user input

Affected if Shortcode attributes contain potentially malicious scripts or unexpected characters
Check for existing XSS payloads in content

Search post content for patterns like 'javascript:', 'onerror=', 'onload=', or other script injection attempts within shortcode attributes

Affected if Malicious JavaScript payloads are found in shortcode attribute values

User is affected if the Slider Bootstrap Carousel plugin is installed with an unpatched version AND the vulnerable shortcode is being used with user-controllable category or template attributes that could contain malicious script tags.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update to a patched version that properly escapes shortcode attributes using esc_attr() before output. Until patched, audit existing content for malicious shortcodes and consider restricting shortcode usage permissions.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing2.0 h
Review / QA1.0 h

8.0 hours of engineering $1,420

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-4076?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 6.4 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Remediation

Need this fixed?

Have this fixed 8 hrs · Moderate

Typical engagement from $1,420

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-4076 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References