Security readout for executives and security teams
Plain-English summary
This vulnerability affects the Leadfox for WordPress plugin through version 2.1.9. A tricked site administrator could be forced into making a request that results in stored cross-site scripting. That can affect site content, visitors, and trust in the website.
Executive priority
Treat this as a high-priority WordPress plugin exposure if Leadfox is deployed. Prioritize inventory first, then update or remove the plugin based on official vendor guidance.
Technical view
CVE-2025-31585 is a CSRF issue in the WordPress leadfox plugin, described as CSRF to stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges, and required user interaction. The provided data does not name a fixed version.
Likely exposure
Exposure is limited to WordPress sites running Leadfox for WordPress, reportedly through version 2.1.9. Asset inventory is required because the provided affected-product metadata is sparse and partly inconsistent.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires user interaction, likely involving a logged-in user being induced to trigger an unwanted request.
Researcher notes
The bundle contains a version discrepancy: the title references <= 2.1.8, while the description says through <= 2.1.9. Use <= 2.1.9 for conservative exposure tracking until vendor data clarifies it.
Mitigation direction
- Inventory WordPress sites for the Leadfox plugin and installed version.
- Check vendor and Patchstack guidance for a fixed release or official mitigation.
- Update the plugin if an official fixed version is available.
- Disable or remove the plugin where it is not business-critical.
- Review CMS audit logs for unexpected Leadfox-related changes.
Validation and detection
- Confirm whether Leadfox for WordPress is installed on each WordPress site.
- Record installed versions and compare against the <= 2.1.9 affected range.
- Check whether administrators recently reported suspicious links or unexpected prompts.
- Review site content and plugin settings for unauthorized changes.
- Verify remediation status against current vendor or Patchstack advisories.
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-31585 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.
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.7Primary CVE scoreVulnerability 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
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.