Security readout for executives and security teams
Plain-English summary
CVE-2025-31457 is a CSRF issue in the WordPress LWS SMS plugin through version 2.4.1. A victim must interact with attacker-controlled content, but the sources do not specify the affected action. Business impact is likely limited integrity or availability disruption on sites using this plugin.
Executive priority
Treat as a moderate-priority WordPress plugin issue. It does not show confirmed exploitation in the supplied sources, but affected public sites should be inventoried and remediated because CSRF can cause unauthorized actions through trusted user sessions.
Technical view
The issue is CWE-352 Cross-Site Request Forgery in Aurélien LWS LWS SMS, package lws-sms, affecting versions through 2.4.1. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress installations running the LWS SMS plugin at version 2.4.1 or earlier. The supplied metadata provides no CPEs and does not identify specific vulnerable endpoints or actions.
Exploitation context
The CVE is not listed as KEV, and the supplied sources do not cite active exploitation. Exploitation requires user interaction. The sources do not provide enough detail to confirm whether administrator interaction is required.
Researcher notes
Evidence is sparse. Patchstack is the only listed advisory reference, and the bundle does not include vulnerable action names, endpoint details, proof of exploitation, or a fixed version. Base validation on plugin presence and version until vendor guidance adds specifics.
Mitigation direction
- Inventory WordPress sites for the LWS SMS plugin and record installed versions.
- Update LWS SMS if vendor or Patchstack guidance identifies a fixed version.
- Disable or remove the plugin where SMS functionality is not required.
- Restrict WordPress administrator access and enforce anti-phishing controls.
- Monitor vendor and Patchstack advisories for remediation details.
Validation and detection
- Confirm whether each WordPress site runs package lws-sms.
- Flag LWS SMS versions 2.4.1 or earlier for remediation review.
- Check Patchstack and CVE records for updated affected-version or fix details.
- Review recent plugin-related settings changes for unexpected activity.
- Avoid production exploit reproduction without explicit authorization.
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-31457 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
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
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:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
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.