Security readout for executives and security teams
Plain-English summary
Social Links for WordPress through version 1.0.11 is reported vulnerable to cross-site request forgery. An attacker may be able to induce an authorized user to perform an unintended action. The supplied title and reference also suggest stored script injection, but the CVE description does not clearly confirm that impact.
Executive priority
Treat as a moderate, near-term remediation item. Prioritize internet-facing WordPress sites and installations used by privileged staff. Escalate if unexpected stored content or administrative changes are found. Current evidence does not justify claiming an active exploitation emergency.
Technical view
CVE-2025-25137 is classified as CWE-352 with CVSS 3.1 score 6.5. The vector indicates network access, low complexity, low privileges, user interaction, changed scope, and low confidentiality, integrity, and availability impacts. Source metadata conflicts on whether this is CSRF alone or CSRF leading to stored XSS.
Likely exposure
Potential exposure is limited to WordPress sites running the Social Links plugin through version 1.0.11. The available data does not identify affected settings, vulnerable actions, installation prevalence, or a confirmed fixed version. Sites without this plugin are not indicated as exposed.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no supplied source establishes active exploitation. Successful abuse appears to require user interaction; the CVSS vector also records low privileges. No conclusion about public exploit availability can be drawn from the evidence.
Researcher notes
The supplied record is internally inconsistent: its description identifies CSRF, while the title and Patchstack reference imply CSRF-to-stored-XSS. The affected-version structure also contains “n/a” despite stating through 1.0.11. Validate the precise vulnerable action, prerequisites, impact, and fixed version against authoritative guidance before final disposition.
Mitigation direction
- Inventory WordPress sites for the Social Links plugin and record installed versions.
- Check current vendor and Patchstack guidance for a fixed release or official mitigation.
- Update to a confirmed fixed version when authoritative guidance identifies one.
- Disable or remove the plugin where it is unnecessary or no supported fix exists.
- Limit privileged WordPress access and avoid untrusted links while remediation is pending.
Validation and detection
- Confirm whether Social Links is installed and whether its version is 1.0.11 or earlier.
- Review plugin release notes and authoritative guidance for the first confirmed fixed version.
- Verify the plugin is updated, disabled, or removed on every identified site.
- Review administrative activity and stored plugin content for unexpected changes.
- Confirm least-privilege access for accounts able to manage the plugin.
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-25137 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
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/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:L/UI:R/S:C/C:L/I:L/A:L2.33.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/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-links/vulnerability/wordpress-facilita-form-tracker-plugin-1-0-csrf-to-stored-xss-vulnerability-2?_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.