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

CVE-2025-62110

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 Rescue Themes Rescue Shortcodes allows Stored XSS.This issue affects Rescue Shortcodes: from n/a through 3.3.

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 Cross-site Scripting (XSS) vulnerability in the Rescue Themes Rescue Shortcodes WordPress plugin allows attackers to inject malicious JavaScript through shortcode parameters. The plugin fails to properly sanitize and encode user input before rendering it in web pages, causing the malicious script to execute in browsers of users who view the affected content.

MitigationUpgrade to the latest version of Rescue Shortcodes when available, or implement proper input sanitization using WordPress sanitization functions (such as esc_attr(), esc_html(), or wp_kses()) and output encoding for all shortcode attributes before rendering. Validate and escape all user-supplied data before displaying.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

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 Rescue Shortcodes plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Rescue Shortcodes' or 'Rescue Themes'. Note the installed version from the plugin details.
    Affected if The plugin is installed and active, making the environment potentially vulnerable.
  2. Identify installed plugin version
    Click on the plugin in the WordPress plugins list to view version details, or check the plugin header in /wp-content/plugins/rescue-shortcodes/ directory via file manager or FTP.
    Affected if No specific version data is provided; compare your version to the latest available version to determine if updates are needed.
  3. Locate shortcode usage in content
    Search WordPress database for shortcode instances: look for [rescue_ shortcodes in wp_posts table, or use a plugin/search to find all posts/pages containing shortcodes like [rescue_ or similar patterns.
    Affected if Shortcodes are present in stored content, meaning unsanitized user input within shortcode attributes could be executed.
  4. Inspect shortcode attribute handling in plugin code
    Access the plugin file (typically rescue-shortcodes.php or similar in /wp-content/plugins/rescue-shortcodes/) and search for add_shortcode function. Check if shortcode attributes are processed with sanitization functions like esc_attr(), esc_html(), or wp_kses() before output.
    Affected if Shortcode attributes are output without proper sanitization functions, confirming the vulnerability exists.
  5. Check stored content for malicious scripts
    Review pages/posts using the shortcodes in a browser or inspect the raw post_content in the database for script tags or javascript: URIs that may have been injected into shortcode parameters.
    Affected if Malicious scripts are found stored in shortcode parameters, indicating active exploitation of the stored XSS.

The environment is affected if the Rescue Shortcodes plugin is installed and shortcode attributes are rendered without sanitization, allowing stored scripts to execute in user browsers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of Rescue Shortcodes when available, or implement proper input sanitization using WordPress sanitization functions (such as esc_attr(), esc_html(), or wp_kses()) and output encoding for all shortcode attributes before rendering. Validate and escape all user-supplied data before displaying.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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