Security readout for executives and security teams
Plain-English summary
WordPress sites running the IceStats plugin through version 1.3 may let an attacker trick a user into saving malicious content that later runs in browsers. This can affect site visitors or administrators depending on where the stored content appears.
Executive priority
Treat this as a high-priority WordPress plugin exposure where the plugin is installed. Prioritize public-facing or business-critical WordPress sites first.
Technical view
The sources describe a CSRF weakness in ronnybull IceStats, package icestats, leading to stored cross-site scripting. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress installations using IceStats through version 1.3. The bundle does not identify other affected products or deployment patterns.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Successful abuse depends on user interaction, consistent with CSRF and the CVSS vector.
Researcher notes
Evidence is limited to the CVE record and Patchstack entry. The bundle names CSRF to stored XSS but does not provide patch details, proof of exploitation, or deeper affected-version metadata beyond through 1.3.
Mitigation direction
- Inventory WordPress sites for the IceStats or icestats plugin.
- Check Patchstack and vendor guidance for a fixed version or official workaround.
- Update the plugin if a fixed release is available.
- If no maintained fix exists, disable or remove the plugin.
- Review WordPress roles and reduce unnecessary administrator sessions.
Validation and detection
- Confirm whether IceStats is installed on each WordPress site.
- Record the installed plugin version and flag versions through 1.3.
- Review recent administrator activity for unexpected plugin or content changes.
- Inspect rendered plugin-controlled content for unexpected script behavior.
- Verify remediation by confirming the vulnerable version is no longer active.
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-53724 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/icestats/vulnerability/wordpress-icestats-plugin-1-3-csrf-to-stored-cross-site-scripting-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.