CVE-2024-51632
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Sam Hoe SH Slideshow sh-slideshow allows Stored XSS.This issue affects SH Slideshow: from n/a through <= 4.3.
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 confidenceA CSRF vulnerability in the SH Slideshow WordPress plugin allows authenticated or unauthenticated attackers to inject malicious JavaScript code through forged requests. The Stored XSS is triggered when the injected payload is rendered in the slideshow, executing in the context of other users' browsers viewing the content.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SH Slideshow plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'SH Slideshow' or check the /wp-content/plugins/ directory for a folder named 'sh-slideshow' or similar. Note the installed version from the plugin header.Affected if The plugin is installed and no version is listed or the version falls within the vulnerable range.
-
Locate state-changing form endpointsNavigate the plugin settings, create/edit slideshow pages, or any admin pages where users can add, edit, or save slideshow content. Identify the form action URLs and any AJAX endpoints the plugin uses.Affected if The plugin has forms or endpoints that accept and store user input.
-
Inspect forms for anti-CSRF tokensView the HTML source of the identified forms. Look for input fields named 'nonce', '_wpnonce', 'security', or similar tokens. Check if the form submission includes this token in the request.Affected if Forms lack nonce fields or the token is not validated server-side on submission.
-
Test for CSRF vulnerabilitySubmit a state-changing request (such as saving a slideshow with a test payload) without including any nonce or token. Use a tool like Burp Suite or curl to send a forged request without the expected token.Affected if The request succeeds and data is saved without requiring a valid CSRF token.
-
Verify stored XSS in slideshow outputAfter injecting a test payload (such as <script>alert(1)</script>) via a forged request, view the slideshow on the frontend. Inspect the page source to see if the payload is rendered as plain text or executed as JavaScript.Affected if The injected payload is executed in the browser when viewing the slideshow.
If the SH Slideshow plugin is installed and its forms/endpoints lack proper nonce validation, the CSRF vulnerability exists and stored XSS can be triggered.
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 dataImplement anti-CSRF tokens (nonce validation) on all state-changing form actions and endpoints, combined with proper input sanitization and output encoding to prevent XSS execution.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51632 — 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-51632 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