Security readout for executives and security teams
Plain-English summary
A WordPress plugin used to manage scripts and tags can be abused through CSRF to store malicious script in the site if a targeted user is tricked into taking an action. That can affect visitor or admin trust and may expose limited data or alter site behavior.
Executive priority
Treat this as a high-priority WordPress exposure where the plugin is installed. Prioritize externally facing marketing or lead-generation sites because stored XSS can damage trust, capture limited user data, or alter site behavior.
Technical view
CVE-2025-31460 affects OmniLeads Scripts and Tags Manager through version 1.3. The reported flaw is CSRF leading to stored XSS, scored CVSS 3.1 7.1 with network attack vector, low complexity, no privileges required, and user interaction required.
Likely exposure
Exposure is limited to WordPress sites running the OmniLeads Scripts and Tags Manager plugin at version 1.3 or earlier. The bundle does not identify a patched version or confirm active exploitation.
Exploitation context
The CVE is not listed as KEV in the provided data, and no supplied source states active exploitation. The attack requires user interaction and results in stored XSS through a CSRF path, not direct unauthenticated code execution.
Researcher notes
The source bundle identifies CWE-352 and describes CSRF to stored XSS, but it does not include exploit details, a fixed version, or vendor remediation text. Affected-version metadata appears sparse, so validate against installed plugin versions and authoritative vendor/Patchstack records.
Mitigation direction
- Inventory WordPress sites for the affected plugin and versions.
- Check Patchstack and vendor guidance for a patched release or official mitigation.
- Disable or remove the plugin where it is not business-critical.
- Limit administrator sessions and use strong anti-phishing controls until remediated.
- Review stored scripts and tag settings for unauthorized changes.
Validation and detection
- Confirm whether the plugin is installed and at version 1.3 or earlier.
- Review WordPress admin configuration for unexpected script or tag entries.
- Check web and WordPress logs for suspicious admin-triggered changes.
- Verify any update target against vendor or Patchstack guidance.
- Document remediation status per affected WordPress instance.
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-31460 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
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.