Security readout for executives and security teams
Plain-English summary
CVE-2024-53779 affects the WordPress Yahoo! WebPlayer plugin through version 2.0.6. A victim could be tricked into making an unwanted browser request that stores malicious script content. Business risk is highest for WordPress sites that still run this old plugin, because stored XSS can affect visitors or administrators later.
Executive priority
Treat this as a high-priority WordPress exposure if the plugin is present. It is not known to be actively exploited from the provided evidence, but stored XSS can create persistent site compromise risk and should be handled during the next urgent web security maintenance window.
Technical view
The issue is a CWE-352 CSRF vulnerability in 8bitkid Yahoo! WebPlayer, package yahoo-media-player, reported as CSRF to stored XSS. It is rated CVSS 3.1 7.1 with network attack vector, low complexity, no privileges required, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to WordPress installations with Yahoo! WebPlayer yahoo-media-player installed at version 2.0.6 or earlier. The source bundle does not identify affected endpoints, deployment prevalence, or whether the plugin remains actively maintained.
Exploitation context
The bundle does not show CISA KEV listing or other cited evidence of active exploitation. CVSS indicates user interaction is required. The available sources do not include exploit code, attack telemetry, or detailed preconditions beyond the affected plugin and version range.
Researcher notes
Evidence is thin beyond the CVE metadata and Patchstack database entry. Do not assume endpoint details, exploit availability, or a specific patch version from this bundle. Validation should focus on confirming plugin presence, version, official remediation status, and signs of stored script injection.
Mitigation direction
- Inventory WordPress sites for yahoo-media-player and record installed versions.
- Check vendor or Patchstack guidance for a fixed release or official mitigation.
- Disable or remove the plugin where it is not business-critical.
- Prioritize remediation on public WordPress sites and administrator-facing deployments.
- Review WordPress administrator accounts and recent content changes for suspicious scripts.
Validation and detection
- Confirm whether yahoo-media-player is installed on each WordPress site.
- Verify installed plugin version is greater than 2.0.6, if a fixed version exists.
- Check security advisories for official remediation status before closing the finding.
- Review stored plugin settings and affected pages for unexpected script content.
- Document compensating controls if the plugin cannot be removed promptly.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2024-53779 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/yahoo-media-player/vulnerability/wordpress-yahoo-webplayer-plugin-2-0-6-csrf-to-stored-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.