dbcve.org
Master Slider ProWordPress extension · Averta

CVE-2025-63045

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 3.7.12 or later.
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 averta Master Slider Pro masterslider allows DOM-Based XSS.This issue affects Master Slider Pro: from n/a through <= 3.7.12.

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

DOM-based Cross-site Scripting vulnerability in Master Slider Pro plugin allows attackers to inject malicious JavaScript through unsanitized input that gets rendered in the web page DOM. The vulnerability exists in how the plugin handles user-controlled data without proper output encoding.

MitigationUpdate Master Slider Pro to the latest version which should contain patched code, or implement proper output encoding/escaping on all user input paths that flow to the DOM in the affected plugin code.

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
Master Slider ProWordPress extension
Affected:< 3.7.12

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. Confirm Master Slider Pro is installed
    Check your WordPress plugins directory or plugin admin panel for 'Master Slider Pro' or 'Averta Master Slider Pro' in the list of installed plugins
    Affected if The plugin is installed and active
  2. Identify the installed version
    Navigate to WordPress admin > Plugins > Master Slider Pro and view the plugin details to find the version number, or check the plugin's main PHP file for the version definition
    Affected if The installed version is any version lower than 3.7.12
  3. Check for active sliders with user-controlled content
    Review all configured sliders in the Master Slider Pro admin panel. Look for text layers, custom slides, or any content fields that accept user input
    Affected if There are active sliders with user-supplied content that could be rendered to the DOM without sanitization
  4. Inspect the DOM for suspicious script injections
    Use browser developer tools (F12) to inspect the page source and DOM. Look for any unexpected <script> tags, event handlers (onload, onerror, onclick), or javascript: URIs in slider-related elements
    Affected if Unexpected scripts or malicious event handlers are present in the DOM related to Master Slider content

Your environment is affected if Master Slider Pro versions below 3.7.12 are installed and active with sliders that render user input to the webpage DOM.

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 3.7.12 or later
Fixed in 3.7.12
Interim mitigation

Update Master Slider Pro to the latest version which should contain patched code, or implement proper output encoding/escaping on all user input paths that flow to the DOM in the affected plugin code.

Recommended fix Moderate confidence

Master Slider Pro 3.7.12 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate 'Master Slider Pro' in the plugin list.
  4. 4. Click 'Update now' if an update is available, or download version 3.7.12 or later from a trusted source such as the official WordPress repository or the vendor's website.
  5. 5. Verify the installed version after update matches 3.7.12 or higher to confirm the patch is applied.

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

Fix this in Master Slider Pro 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-63045 — 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-63045 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