CVE-2024-51647
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 Chaser324 Featured Posts Scroll allows Stored XSS.This issue affects Featured Posts Scroll: from n/a through 1.25.
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 Featured Posts Scroll WordPress plugin (versions up to 1.25) allows attackers to forge administrative requests that inject malicious JavaScript, resulting in stored XSS. When administrators view the affected pages, the injected payload executes in their browser session.
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.
-
Confirm plugin is installedGo to WordPress admin dashboard > Plugins and look for 'Featured Posts Scroll' in the installed plugins list, or check the plugin files in /wp-content/plugins/featured-posts-scroll/Affected if Plugin is present in the WordPress installation
-
Identify installed versionIn Plugins page, click on the plugin to view details and read the version number, or check the main plugin PHP file for the 'Version' header commentAffected if Version is 1.25 or any earlier version (1.0 through 1.25)
-
Check for vulnerable AJAX endpointsInspect the plugin directory for AJAX handlers (wp_ajax_ hooks) in files like featured-posts-scroll.php or includes/*.php - look for save/update functions that process user input without verifying noncesAffected if AJAX endpoints exist that lack wp_verify_nonce or check_admin_referer calls before processing data
-
Inspect form submissions for nonce protectionReview plugin PHP files for form HTML output (settings pages, admin panels) - search for 'form' tags and verify they include wp_nonce_field or wp_nonce_url callsAffected if Forms lack nonce fields or nonce verification on submission
-
Check for stored XSS entry pointsExamine how the plugin handles and displays post/feature data - look for output functions like echo or print that insert database values without esc_html, esc_attr, or similar escaping functionsAffected if User-supplied data is stored and displayed without proper output escaping
If Featured Posts Scroll plugin version 1.25 or earlier is installed and its forms or AJAX endpoints lack nonce verification, the environment is vulnerable to CVE-2024-51647.
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 WordPress nonces on all forms and AJAX endpoints to prevent CSRF, and apply proper output escaping and input sanitization to prevent stored XSS.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51647 — 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-51647 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