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

CVE-2026-2480

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-31
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 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 WP Shortcodes Plugin — Shortcodes Ultimate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'max_width' attribute of the `su_box` shortcode in all versions up to, and including, 7.4.10 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 confidence

The Shortcodes Ultimate WordPress plugin versions up to 7.4.10 contain a stored XSS vulnerability in the su_box shortcode's max_width attribute. Due to insufficient input sanitization and output escaping, authenticated users with contributor-level permissions or higher can inject arbitrary JavaScript that executes whenever the affected page is accessed.

MitigationUpdate the Shortcodes Ultimate plugin to version 7.4.11 or later which contains the fix. Until patched, consider restricting shortcode usage permissions to trusted roles or temporarily disabling the su_box shortcode.

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 Shortcodes Ultimate plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Shortcodes Ultimate'. Note the installed version number displayed next to the plugin name.
    Affected if Plugin is installed and version is 7.4.10 or lower
  2. Confirm the vulnerable shortcode exists
    Search your WordPress database for instances of the su_box shortcode. This can be done via phpMyAdmin by querying the wp_posts table for post_content containing '[su_box' or by using a plugin like Search Replace DB.
    Affected if Any post, page, or widget content contains the su_box shortcode
  3. Check for unpatched version
    Compare the installed version from step 1 against the affected range: versions 7.0.0 through 7.4.10 are vulnerable. Version 7.4.11 and later contain the fix.
    Affected if Installed version is 7.4.10 or lower
  4. Identify users with contributor-level access
    In WordPress admin, go to Users > All Users and review the Role column. Users assigned 'Contributor', 'Author', 'Editor', or Administrator roles can access shortcode insertion functionality.
    Affected if Any user with Contributor role or higher exists on the site
  5. Inspect su_box shortcode max_width usage
    Review posts/pages containing su_box shortcode. If max_width attribute is present with custom values (anything other than default), examine whether the value contains quotes, script tags, or unusual characters that could indicate exploitation.
    Affected if su_box shortcode with max_width attribute is found in published content

You are affected if the Shortcodes Ultimate plugin version is 7.4.10 or lower AND the su_box shortcode is used somewhere on your site with contributor-level or higher user accounts present.

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 Shortcodes Ultimate plugin to version 7.4.11 or later which contains the fix. Until patched, consider restricting shortcode usage permissions to trusted roles or temporarily disabling the su_box shortcode.

Recommended fix High confidence

Shortcodes Ultimate version 7.4.11 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Shortcodes Ultimate plugin
  4. Click 'Update now' if an update is available, or manually update to version 7.4.11 or higher
  5. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,010
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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