dbcve.org
Bootstrap Shortcodes UltimateWordPress extension · Addonmaster

CVE-2023-47851

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to after 4.3.1 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 Akhtarujjaman Shuvo Bootstrap Shortcodes Ultimate allows Stored XSS.This issue affects Bootstrap Shortcodes Ultimate: from n/a through 4.3.1.

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 XSS vulnerability in the Bootstrap Shortcodes Ultimate WordPress plugin allows authenticated attackers to inject malicious JavaScript through plugin shortcodes. The unsanitized input is stored in the database and executed when other users view pages containing the affected shortcodes.

MitigationUpdate to the latest patched version of Bootstrap Shortcodes Ultimate. If no patch is available, remove the plugin or implement WAF rules to block XSS attack patterns. Alternatively, audit and add proper input sanitization and output encoding to all shortcode handlers.

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
Bootstrap Shortcodes UltimateWordPress extension
Affected:<= 4.3.1

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. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > find 'Bootstrap Shortcodes Ultimate' and view the version number. Alternatively, check the plugin's main PHP file header for the Version field.
    Affected if The installed version is 4.3.1 or lower.
  2. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm that 'Bootstrap Shortcodes Ultimate' is activated.
    Affected if The plugin is active and the version is 4.3.1 or lower.
  3. Inspect pages and posts using plugin shortcodes
    Search the WordPress database (wp_posts table) for content containing shortcode patterns like [bsu_] or shortcodes specific to this plugin. Check the post_content field for any unexpected script tags, javascript: URIs, or event handlers like onload, onerror, onmouseover.
    Affected if Any post or page content contains the plugin shortcodes with unsanitized user-supplied input that includes script tags or JavaScript event handlers.
  4. Review recent user submissions for XSS payloads
    Query the wp_posts table for recent posts/pages created by users, looking for patterns like <script>, javascript:, onerror=, onload=, onmouseover=, and other HTML event attributes within shortcode attribute values.
    Affected if Database contains posts with shortcode attributes containing XSS payloads such as script tags or JavaScript event handlers.

You are affected if Bootstrap Shortcodes Ultimate version 4.3.1 or lower is installed and active, and any page or post content contains the plugin's shortcodes with unsanitized input that includes script tags or JavaScript event handlers.

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.

From vendor data
Upgrade available Upgrade to a release after 4.3.1
Interim mitigation

Update to the latest patched version of Bootstrap Shortcodes Ultimate. If no patch is available, remove the plugin or implement WAF rules to block XSS attack patterns. Alternatively, audit and add proper input sanitization and output encoding to all shortcode handlers.

Fix this in Bootstrap Shortcodes Ultimate Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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