Master SliderWordPress extension · Averta
CVE-2024-4375
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 · uneditedThe Master Slider – Responsive Touch Slider plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'ms_layer' shortcode in all versions up to, and including, 3.9.10 due to insufficient input sanitization and output escaping on the 'css_id' user supplied attribute. 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. e CVE-2024-37222 may be a duplicate of this issue.
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 confidenceStored XSS vulnerability in the Master Slider WordPress plugin where the 'ms_layer' shortcode does not properly sanitize the 'css_id' attribute before outputting it, allowing authenticated attackers with contributor-level access to inject malicious JavaScript that executes when users view affected pages.
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
<= 3.9.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Master Slider plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Master Slider' or check the plugins directory for 'masterslider' folderAffected if Master Slider plugin is present on the WordPress site
-
Check installed Master Slider versionIn WordPress admin, go to Plugins > Installed Plugins, find Master Slider, and note the version number displayedAffected if Version is 3.9.10 or lower (any version up to and including 3.9.10)
-
Identify ms_layer shortcode usage in contentSearch WordPress database for posts containing '[ms_layer' shortcode using: SELECT ID, post_type FROM wp_posts WHERE post_content LIKE '%[ms_layer%'Affected if Any ms_layer shortcode is found in published content
-
Inspect css_id attribute in shortcodesSearch database content for 'css_id=' within ms_layer shortcodes: SELECT ID FROM wp_posts WHERE post_content LIKE '%[ms_layer%css_id=%'Affected if The css_id attribute is present in any ms_layer shortcode
-
Analyze css_id values for injection patternsExtract and review all css_id values from shortcodes, looking for unescaped characters like quotes, brackets, or script keywords that could indicate XSS payloadAffected if css_id contains unsanitized user input with special characters that could execute as JavaScript
User is affected if Master Slider plugin version 3.9.10 or lower is installed AND the ms_layer shortcode with a css_id attribute is present in any published content.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Master Slider plugin to the latest version which contains the fix, or implement proper input sanitization using functions like sanitize_html_class() on the css_id parameter before output.
Fix this in Master Slider
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4375 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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