dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-31460

HIGH · 7.1 CVSS v3.1 Published 2025-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in danielmuldernl OmniLeads Scripts and Tags Manager omnileads-scripts-and-tags-manager allows Stored XSS.This issue affects OmniLeads Scripts and Tags Manager: from n/a through <= 1.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a chained CSRF-to-Stored-XSS vulnerability in the OmniLeads Scripts and Tags Manager plugin. An attacker can trick an authenticated administrator into submitting a malicious request that stores malicious JavaScript code within the Scripts and Tags Manager functionality. When other users view or interact with the stored content, the XSS payload executes in their browsers.

MitigationImplement anti-CSRF tokens on all state-changing operations in the Scripts and Tags Manager and apply output encoding/sanitization when rendering stored scripts and tags to prevent XSS execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify OmniLeads installation
    Identify if OmniLeads is installed in your environment by checking for the application directories or running 'omni-leads version' if a CLI tool exists
    Affected if OmniLeads is not installed, this CVE does not apply
  2. Confirm Scripts and Tags Manager is enabled
    Access the OmniLeads admin interface and navigate to the Scripts and Tags Manager plugin section to verify it is active
    Affected if The Scripts and Tags Manager plugin is not enabled, the vulnerability cannot be exploited
  3. Inspect stored scripts and tags for malicious content
    Review all entries in the Scripts and Tags Manager database table or UI for any suspicious JavaScript code, such as <script> tags, event handlers (onload, onerror, onclick), or javascript: URIs
    Affected if Any stored script or tag contains executable JavaScript that was not authored by a trusted administrator
  4. Verify CSRF protection on Scripts and Tags Manager endpoints
    Examine the HTTP requests when creating/editing scripts or tags; check if a CSRF token or anti-CSRF header is included in the request
    Affected if State-changing operations in Scripts and Tags Manager lack CSRF tokens, allowing attackers to forge requests on behalf of administrators

You are affected if OmniLeads with the Scripts and Tags Manager plugin is installed and either malicious scripts are stored in the system or CSRF protections are missing from the plugin's endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens on all state-changing operations in the Scripts and Tags Manager and apply output encoding/sanitization when rendering stored scripts and tags to prevent XSS execution.

Recommended fix Moderate confidence

Update to a version greater than 1.3 (check WordPress plugin repository or vendor for latest fixed release)

  1. 1. Check the current version of the OmniLeads Scripts and Tags Manager plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the OmniLeads Scripts and Tags Manager plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update completed successfully
  6. 6. Test the plugin functionality to ensure it works correctly after the update
  7. 7. If no update is available in the WordPress plugin repository, contact the plugin developer (danielmuldernl) for the patched version or check the vendor's website for updates
Caveat Review plugin settings after upgrade as minor functionality changes may occur with version updates

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31460 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data