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

CVE-2025-30564

HIGH · 7.1 CVSS v3.1 Published 2025-03-24
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 wpwox Custom Script Integration custom-script-integration allows Stored XSS.This issue affects Custom Script Integration: from n/a through <= 2.1.

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 · high confidence

A CSRF vulnerability in wpwox Custom Script Integration plugin versions <= 2.1 allows attackers to craft malicious requests that inject persistent JavaScript payloads (Stored XSS). When authenticated administrators or users access the affected script injection points, the embedded malicious code executes in their browsers.

MitigationUpdate the Custom Script Integration plugin to the latest patched version immediately. Additionally, implement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX actions within the plugin to prevent forged requests.

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 plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Custom Script Integration' by wpwox in the list
    Affected if The plugin is present in the WordPress installation
  2. Check installed version
    In the plugins list, locate the version number displayed under the plugin name 'Custom Script Integration'
    Affected if Version number is 2.1 or lower (e.g., 2.1, 2.0.5, 1.x)
  3. Identify script injection points
    Access the plugin settings page (usually under Settings or a dedicated wpwox menu) and locate fields labeled as script injection, custom script, or code injection areas
    Affected if The plugin provides fields where custom JavaScript/CSS can be entered and saved to the database
  4. Inspect stored script content
    Check the WordPress database (typically the wp_options table or a custom plugin table) for entries related to custom_script, script_integration, or wpwox custom scripts containing unsanitized script tags
    Affected if Database contains script entries with unescaped HTML/script tags that could execute in admin sessions
  5. Verify nonce protection absence
    Inspect the plugin PHP source files for form submissions and AJAX actions - look for missing wp_nonce_field() or check_admin_referer() calls on the plugin's settings and script injection forms
    Affected if Plugin forms handling script injection lack WordPress nonce verification

If the Custom Script Integration plugin version is 2.1 or lower and the plugin provides active script injection features without proper nonce validation, the environment is affected by this CSRF-to-Stored-XSS vulnerability.

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

Update the Custom Script Integration plugin to the latest patched version immediately. Additionally, implement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX actions within the plugin to prevent forged requests.

Recommended fix Moderate confidence

Custom Script Integration version > 2.1 (latest version available from vendor)

  1. Contact wpwox (the plugin vendor) to confirm the latest patched version of Custom Script Integration
  2. Navigate to WordPress admin > Plugins > Installed Plugins
  3. Locate the Custom Script Integration plugin
  4. Update the plugin to the latest available version from the WordPress repository or vendor

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30564 — 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-30564 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