CVE-2024-51650
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 scottmydollarplancom Random Featured Post random-featured-post-plugin allows Stored XSS.This issue affects Random Featured Post: from n/a through <= 1.1.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 confidenceThis is a CSRF vulnerability in the Random Featured Post WordPress plugin that enables Stored XSS attacks. Attackers can exploit the lack of CSRF protection to trick authenticated administrators into submitting malicious requests that inject persistent JavaScript payloads into the plugin's stored data, which then executes when other users view affected pages.
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 Random Featured Post plugin is installedGo to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Random Featured Post' or review the plugin list for this specific pluginAffected if The plugin appears in the installed plugins list
-
Identify installed plugin versionClick on the plugin in the Plugins list to view details, or check the plugin header in /wp-content/plugins/random-featured-post/ directory for the Version commentAffected if The installed version matches or falls within any affected version range for this CVE (compare your version to the affected ranges if known)
-
Verify plugin is activeCheck the Plugins list status - the plugin must show as 'Active' under the plugin nameAffected if The plugin status shows as Active
-
Inspect plugin stored data for malicious contentNavigate to the plugin settings page (usually under Settings or a dedicated menu item for Random Featured Post) and examine all text fields, post selections, or configuration options for suspicious HTML, script tags, or encoded JavaScript payloadsAffected if Any plugin configuration fields contain unexpected script tags, event handlers (onclick, onerror, etc.), or other XSS payloads
-
Check plugin source for nonce verificationIf you have file access, examine the plugin PHP files in /wp-content/plugins/random-featured-post/ - look for wp_nonce_field, wp_verify_nonce, or check_admin_referer calls in form handlers and AJAX actionsAffected if Form processing code lacks nonce verification logic or contains no CSRF token checks
You are affected if the Random Featured Post plugin is installed, active, and either runs an affected version or shows evidence of unauthorized script injection in its stored configuration data.
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 admin forms and AJAX actions, verify nonces on form processing endpoints, and properly sanitize output when displaying plugin data to prevent XSS.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51650 — 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-51650 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