Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress Social Crowd plugin can let an attacker trick a user into saving malicious script content, which may later run in visitors' or administrators' browsers. The bundle rates this high severity, but it does not show confirmed exploitation or a named fixed version.
Executive priority
Treat this as a high-priority WordPress plugin exposure, especially for sites handling customer traffic or administrator sessions. It is not marked as known exploited in the supplied sources, so prioritize rapid inventory and vendor-guided remediation over emergency incident assumptions.
Technical view
CVE-2025-31390 is a CSRF issue in bdoga Social Crowd through version 0.9.6.1 that can lead to stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges, required user interaction, and changed scope.
Likely exposure
Exposure is limited to WordPress sites with the Social Crowd plugin installed at versions up to and including 0.9.6.1. The source bundle does not identify broader products, hosted platforms, or specific vulnerable configuration paths.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source here confirms active exploitation. The CVSS vector indicates exploitation requires user interaction; exact victim role and triggering workflow are not provided.
Researcher notes
Evidence is limited to the CVE record and Patchstack entry. The bundle identifies CWE-352 and stored XSS impact but does not include request parameters, affected endpoints, proof of concept, fixed version, or exploitation telemetry.
Mitigation direction
- Inventory WordPress sites for the Social Crowd plugin and version.
- Check Patchstack, CVE, and vendor guidance for a fixed release.
- Update the plugin if a trusted fixed version is available.
- If no fix is available, evaluate disabling or removing the plugin.
- Prioritize sites with privileged WordPress users or public traffic.
Validation and detection
- Confirm whether Social Crowd is installed on each WordPress site.
- Record installed plugin versions and flag versions <= 0.9.6.1.
- Review WordPress content and plugin settings for unexpected stored script content.
- Check security logs for suspicious admin actions around plugin settings.
- Document whether vendor guidance names a fixed version or mitigation.
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-31390 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-crowd/vulnerability/wordpress-social-crowd-plugin-0-9-6-1-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.