CVE-2024-51650: WordPress Random Featured Post plugin <= 1.1.3 - CSRF to Stored Cross Site Scripting (XSS) vulnerability
Cross-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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-51650 affects the WordPress Random Featured Post plugin through version 1.1.3. A user can be tricked into causing a stored cross-site scripting change, which may later run in visitors' browsers. The sources rate this high severity, but they do not show active exploitation or a confirmed fixed version.
Executive priority
Treat this as a high-priority WordPress plugin exposure if the plugin is installed. Prioritize discovery and temporary removal where feasible, because stored XSS can affect users and site trust even without confirmed exploitation.
Technical view
The issue is a CSRF vulnerability, CWE-352, in random-featured-post-plugin that can lead to stored XSS. CVSS 3.1 is 7.1: network attack vector, low complexity, no privileges, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites running Random Featured Post, package random-featured-post-plugin, at version 1.1.3 or earlier. Sites not using this plugin are not affected based on the provided sources.
Exploitation context
The bundle does not list CISA KEV status and provides no cited evidence of active exploitation. The CVSS vector requires user interaction, consistent with a CSRF-driven stored XSS scenario.
Researcher notes
Evidence is narrow: CVE data and Patchstack identify CSRF to stored XSS through 1.1.3, with CVSS 7.1. The provided bundle does not include a proof of concept, active exploitation evidence, detailed vulnerable parameter, or confirmed patched release.
Mitigation direction
Inventory WordPress sites for Random Featured Post plugin version 1.1.3 or earlier.
Disable or remove the plugin if it is not business-critical.
Check Patchstack, CVE, and vendor guidance for a fixed version or official mitigation.
Avoid inventing code-level fixes until vendor remediation details are confirmed.
Validation and detection
Confirm whether random-featured-post-plugin is installed on each WordPress instance.
Record the installed plugin version and compare it with the affected range.
Review WordPress administrative content for unexpected stored script-like changes.
Check security advisories for any newly published fix or exploitation evidence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.