SliderWordPress extension · 10web
CVE-2024-32578
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in 10Web Slider by 10Web allows Reflected XSS.This issue affects Slider by 10Web: from n/a through 1.2.54.
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 confidenceReflected XSS vulnerability in the Slider by 10Web plugin (versions through 1.2.54) allows injection of malicious JavaScript via unsanitized user input that gets reflected in the web page without proper encoding.
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
SliderWordPress extension
< 1.2.55CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check if 10web Slider plugin is installedLocate the plugin directory at wp-content/plugins/ and look for a folder named 'slider-wd' or 'slider-by-10web' or similar 10web slider directory. Alternatively, check via WordPress admin under Plugins > Installed Plugins.Affected if The plugin directory exists in the WordPress plugins folder.
-
Identify the installed version of the Slider by 10Web pluginOpen the main plugin PHP file (usually slider-wd/wd-slider.php or similar) and look for the version comment header, or check the readme.txt file for the 'Version' field.Affected if The reported version is below 1.2.55 (e.g., 1.2.54, 1.2.53, etc.).
-
Confirm the plugin is active and accessibleLog into WordPress admin and verify the plugin shows as 'Active' under Plugins > Installed Plugins, or query the WordPress database wp_options table for active_plugins option.Affected if The plugin is installed AND active, making the vulnerable code reachable.
-
Check for user input reflection points (optional - requires code review)Review plugin source code for GET/POST parameters that are echoed or printed directly to HTML output without using functions like esc_html(), esc_attr(), or similar WordPress escaping functions.Affected if The plugin code accepts user input and reflects it to the page without proper encoding - this confirms the vulnerability is present in this installation.
You are affected if the Slider by 10Web plugin is installed, active, and running version 1.2.54 or below.
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.
dbcve · scoped1.2.55
Update to the latest patched version of the plugin that implements proper input sanitization and output encoding, or deploy WAF rules to filter XSS attack patterns.
1.2.55
- Update the Slider by 10Web plugin to version 1.2.55 or higher
- After updating, verify the plugin is running version 1.2.55 or later in the WordPress plugins admin panel
- Test the affected functionality to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Slider
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32578 — 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-32578 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