dbcve.org
Shortcodes UltimateWordPress extension · Getshortcodes

CVE-2025-5567

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-04
Fix available
A fix is available. Upgrade to 7.4.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
The WP Shortcodes Plugin — Shortcodes Ultimate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data-url' DOM element attribute in all versions up to, and including, 7.4.0 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.

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

Stored Cross-Site Scripting vulnerability in the Shortcodes Ultimate WordPress plugin allows authenticated users with Contributor-level access to inject malicious scripts via the 'data-url' DOM element attribute due to insufficient input sanitization and output escaping.

MitigationUpdate the plugin to version 7.4.1 or later which contains the fix for proper input sanitization and output escaping of the 'data-url' attribute.

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
Shortcodes UltimateWordPress extension
Affected:< 7.4.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. Confirm Shortcodes Ultimate plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Shortcodes Ultimate' or 'Getshortcodes' in the list. Alternatively, check the /wp-content/plugins/shortcodes-ultimate/ directory exists on the server.
    Affected if The plugin is not installed or has been removed entirely.
  2. Identify the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Shortcodes Ultimate and note the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/shortcodes-ultimate/shortcodes-ultimate.php for the 'Version' comment.
    Affected if The version number is lower than 7.4.1.
  3. Determine if contributor-level or higher user accounts exist
    In WordPress admin, go to Users > All Users and review the role column. Look for users assigned the 'Contributor' role, or any custom role with permissions equivalent to Contributor or above.
    Affected if There is at least one user with Contributor-level access or higher who could potentially craft and save malicious shortcode content.
  4. Verify if shortcodes containing data-url attributes are in use
    Search the WordPress database (wp_posts table) or site content for instances of shortcode usage, particularly looking for shortcodes that may utilize the data-url attribute. Check posts, pages, and widget content where shortcodes are inserted.
    Affected if Content exists containing shortcodes from this plugin, as the XSS payload would be stored in such content.

A user is affected if the Shortcodes Ultimate plugin version is below 7.4.1 AND there exists at least one user with Contributor-level access AND shortcode content is stored on the site that could contain a malicious data-url value.

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
Upgrade available Upgrade to 7.4.1 or later
Fixed in 7.4.1
Interim mitigation

Update the plugin to version 7.4.1 or later which contains the fix for proper input sanitization and output escaping of the 'data-url' attribute.

Recommended fix High confidence

7.4.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Shortcodes Ultimate plugin in the list
  4. If the plugin shows an available update, click 'Update Now' to upgrade to version 7.4.1 or later
  5. Alternatively, manually upload version 7.4.1 of the plugin via Plugins > Add New > Upload Plugin
  6. After updating, verify the installed version is 7.4.1 or higher

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

Fix this in Shortcodes Ultimate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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