Security readout for executives and security teams
Plain-English summary
CVE-2026-25015 affects the WordPress UsersWP plugin through version 1.2.53. It is a cross-site request forgery issue, meaning an attacker may be able to trick a logged-in user into causing an unintended action. The public data rates it medium severity, with limited integrity impact and no stated confidentiality or availability impact.
Executive priority
Treat this as a moderate WordPress plugin risk. It is not currently flagged as known exploited in the provided data, but internet-facing WordPress sites should be inventoried and remediated promptly once vendor guidance is confirmed, especially where administrative users frequently access the site.
Technical view
The CVE describes CWE-352 in Stiofan UsersWP for WordPress, affecting versions up to and including 1.2.53. CVSS 3.1 is 4.3: network exploitable, low complexity, no attacker privileges, but user interaction required. Scope is unchanged, with low integrity impact only. The supplied sources do not describe the vulnerable action, patch version, or exploit details.
Likely exposure
Exposure is limited to WordPress sites running the UsersWP plugin at version 1.2.53 or earlier. Sites without this plugin are not affected based on the provided sources. Business risk depends on what CSRF-protected action is impacted, which is not specified in the source bundle.
Exploitation context
The CVE requires user interaction, typically a logged-in user being induced to visit or trigger attacker-controlled content. The bundle states KEV is false, and no cited source reports active exploitation. The available public description does not provide enough detail to assess practical exploitability beyond the CVSS vector.
Researcher notes
Public detail is sparse. The record identifies CSRF in UsersWP through 1.2.53 and provides CVSS, but not the affected endpoint, required victim role, nonce failure, or fixed version. Avoid assuming impact beyond low integrity until vendor or Patchstack details clarify the vulnerable action.
Mitigation direction
- Inventory WordPress sites for the UsersWP plugin and record installed versions.
- Prioritize sites running UsersWP version 1.2.53 or earlier.
- Check UsersWP vendor and Patchstack guidance for a fixed version or official mitigation.
- Apply the vendor-recommended update or mitigation when confirmed.
- If risk is unacceptable, consider temporarily disabling the plugin after business approval.
Validation and detection
- Confirm whether each WordPress site has the UsersWP plugin installed.
- Verify the plugin version is greater than 1.2.53, if a fixed release exists.
- Review vendor or Patchstack advisories for updated remediation details.
- Confirm no CISA KEV listing before claiming known active exploitation.
- Document compensating controls if immediate remediation is unavailable.
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-2026-25015 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
- 4.3 (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:N
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:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
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.