Security readout for executives and security teams
Plain-English summary
This vulnerability affects the WordPress Social Analytics plugin through version 0.2. A victim with an active session could be tricked into saving malicious content that later runs in a browser. For businesses, the risk is highest on public WordPress sites still using this older plugin, especially where administrators routinely access the dashboard.
Executive priority
Treat this as a high-priority WordPress exposure review, not a broad enterprise emergency. Prioritize public sites and business-critical sites first. If the plugin is present and no trusted fixed version is available, removal is the clearest risk reduction path supported by the available evidence.
Technical view
The issue is reported as CSRF leading to stored XSS in MartijnScheijbeler Social Analytics social-analytics <=0.2. The CVSS 3.1 score is 7.1, with network attack vector, low complexity, no privileges required, user interaction required, and changed scope. The source bundle does not name a fixed version or vendor mitigation.
Likely exposure
Exposure is limited to WordPress installations with the Social Analytics plugin installed at version 0.2 or earlier. The bundle does not identify other products, hosted services, or confirmed default deployments.
Exploitation context
The CVE is not marked as CISA KEV in the provided bundle. Sources support a CSRF-to-stored-XSS condition, but they do not provide evidence of active exploitation, public exploit use, or exploitation at scale.
Researcher notes
The public description is sparse: CSRF is the listed CWE, while the impact is stored XSS. Validate exposure through installed plugin/version evidence, not product-name matching alone. Do not assume a patch exists from the provided sources; the bundle names no fixed version.
Mitigation direction
- Inventory WordPress sites for the Social Analytics plugin and version.
- Disable or remove Social Analytics if version is 0.2 or earlier.
- Check Patchstack and vendor guidance for any maintained fixed release.
- Limit WordPress administrator sessions to trusted devices and networks.
- Review affected sites for unexpected stored scripts or content changes.
Validation and detection
- Confirm whether social-analytics is installed on each WordPress site.
- Record installed plugin versions and flag 0.2 or earlier.
- Review plugin settings and stored content for unexpected HTML or scripts.
- Check change history and access logs around suspicious admin activity.
- Verify no affected plugin remains enabled after remediation.
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-2025-23743 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/social-analytics/vulnerability/wordpress-social-analytics-plugin-0-2-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.