dbcve.org
VulnerabilityAwaiting classification

CVE-2025-15665

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 6 weeks old

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 Ultimate Before After Image Slider & Gallery WordPress plugin before 4.7.1 does not escape the value of the BEAF Slider widget's shortcode field before outputting it on the front end (the value is passed through do_shortcode, which echoes non-shortcode content verbatim), allowing users with administrator-level access to store a script that executes in the browser of any visitor who loads a page displaying the widget.

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 Ultimate Before After Image Slider & Gallery plugin before version 4.7.1 fails to escape the BEAF Slider widget shortcode field value before outputting it in the frontend. Since do_shortcode passes non-shortcode content through verbatim, an administrator can inject malicious JavaScript that executes in every visitor's browser viewing a page with the widget.

MitigationUpdate the plugin to version 4.7.1 or later. If unavailable, consider removing the plugin until a patch is released.

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
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. Identify plugin installation and version
    Locate the plugin folder in wp-content/plugins/ultimate-before-after-slider-gallery/ (or check via WordPress admin dashboard under Plugins). Open the main plugin PHP file and look for the 'Version' header comment, or run: grep -r 'Version:' wp-content/plugins/ultimate-before-after-slider-gallery/*.php
    Affected if The installed version is lower than 4.7.1 or the version cannot be determined
  2. Detect BEAF shortcode usage on pages
    Search the WordPress database or content files for the [beaf] shortcode. Run: grep -r '\[beaf' wp-content/uploads/ or query the wp_posts table for post_content containing 'beaf'
    Affected if Any page, post, or widget content contains the [beaf] shortcode
  3. Inspect shortcode attributes for unsanitized input
    Examine the shortcode usage found in step 2. Look for patterns like [beaf slider_id="<user_input>"] or [beaf _any_attribute_="<script>"] in the post content. Check if attribute values contain HTML or JavaScript characters like <, >, script, onload, onerror
    Affected if The shortcode attributes contain unescaped HTML, JavaScript tags, or event handler attributes like onerror or onload
  4. Verify frontend output for XSS
    View a page containing the BEAF widget in a browser, then inspect the page source. Search for the raw shortcode attribute values appearing unescaped in the HTML output. Use browser developer tools to examine if user-supplied values in the widget are rendered as plain text or as executable HTML/script
    Affected if User-controlled shortcode attributes appear verbatim in the rendered HTML without HTML encoding

A user is affected if the Ultimate Before After Image Slider & Gallery plugin version is below 4.7.1 AND any page on the site uses the BEAF shortcode with user-supplied attribute values that render unescaped in the frontend.

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 plugin to version 4.7.1 or later. If unavailable, consider removing the plugin until a patch is released.

Recommended fix High confidence

4.7.1

  1. Update the Ultimate Before After Image Slider & Gallery WordPress plugin to version 4.7.1 or later

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
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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