dbcve.org
Master SliderWordPress extension · Averta

CVE-2024-1449

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-02
Fix available
A fix is available. Upgrade to 3.9.10 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 Master Slider – Responsive Touch Slider plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's ms_slide shortcode in all versions up to, and including, 3.9.10 due to insufficient input sanitization and output escaping on the 'src' user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions 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 Master Slider WordPress plugin has a stored XSS vulnerability in the ms_slide shortcode. The 'src' attribute is not properly sanitized when input is received and not escaped when output, allowing authenticated contributors+ to inject arbitrary JavaScript that executes when users view affected pages.

MitigationUpdate to version 3.9.11 or later which contains the patch; alternatively, add sanitization (sanitize_url/esc_url) to the 'src' attribute processing in the shortcode handler and ensure proper output escaping.

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 SliderWordPress extension
Affected:< 3.9.10

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. Verify Master Slider plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Master Slider' plugin appears in the installed plugins list. Note its activation status.
    Affected if Plugin is installed and active
  2. Check installed Master Slider version
    In WordPress admin > Plugins, find Master Slider and compare the version number against 3.9.10. The version may be visible in the plugin row or by viewing the plugin file header (typically in master-slider.php).
    Affected if Version is lower than 3.9.10 (e.g., 3.9.9, 3.9.8, etc.)
  3. Identify usage of ms_slide shortcode
    Search the WordPress database for posts/pages containing the shortcode '[ms_slide' using WP admin search or a database query. Example SQL: SELECT * FROM wp_posts WHERE post_content LIKE '%[ms_slide%' AND post_status != 'trash';
    Affected if Shortcode is present in any published content
  4. Inspect shortcode src attribute handling
    Examine the ms_slide shortcode handler in the plugin files (typically in includes/shortcodes.php or similar). Look for how the 'src' attribute is processed and whether sanitize_url() or esc_url() is applied before output.
    Affected if The 'src' attribute is output without sanitize_url/esc_url sanitization or escaping functions are missing
  5. Verify contributor+ user access
    Check WordPress user roles at Users > All Users. Identify if any users have the Contributor, Author, Editor, or Administrator roles, as any authenticated user with Contributor+ access can exploit this.
    Affected if Any contributor+ level accounts exist in the WordPress installation

The environment is affected if Master Slider plugin version is below 3.9.10 AND the ms_slide shortcode is in use AND untrusted users have contributor+ access to inject malicious src values.

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.9.10 or later
Fixed in 3.9.10
Interim mitigation

Update to version 3.9.11 or later which contains the patch; alternatively, add sanitization (sanitize_url/esc_url) to the 'src' attribute processing in the shortcode handler and ensure proper output escaping.

Recommended fix High confidence

Master Slider version 3.9.10

  1. 1. Backup your WordPress database and files.
  2. 2. Navigate to your WordPress dashboard > Plugins.
  3. 3. Locate Master Slider in the installed plugins list.
  4. 4. Click 'Update Now' if an update is available, or manually download version 3.9.10 from wordpress.org and upload via FTP or the WordPress plugin uploader.
  5. 5. After updating, verify the slider functionality works correctly on your site.
  6. 6. Clear any caching plugins or server-side caches to ensure changes take effect.

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

Fix this in Master Slider Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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