CVE-2025-30564

7.1 HIGH

📋 TL;DR

A Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Custom Script Integration plugin allows attackers to inject malicious scripts via forged requests. When exploited, this can lead to Stored Cross-Site Scripting (XSS) attacks. WordPress sites using Custom Script Integration plugin versions up to 2.1 are affected.

💻 Affected Systems

Products:
  • WordPress Custom Script Integration plugin
Versions: n/a through 2.1
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires the plugin to be installed and activated. Attackers need to trick authenticated users with plugin management privileges.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could inject persistent malicious scripts that execute in visitors' browsers, potentially stealing session cookies, redirecting users to malicious sites, or performing actions on behalf of authenticated users.

🟠

Likely Case

Attackers trick authenticated administrators into clicking malicious links that modify plugin settings to inject JavaScript payloads, affecting all site visitors.

🟢

If Mitigated

With proper CSRF protections and input validation, the vulnerability would be prevented from being exploited.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires social engineering to trick authenticated users into performing actions. The CSRF leads to stored XSS payload injection.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version after 2.1

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/custom-script-integration/vulnerability/wordpress-custom-script-integration-2-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Custom Script Integration' and check if update is available. 4. Click 'Update Now' if update is available. 5. If no update is available, consider disabling or removing the plugin.

🔧 Temporary Workarounds

Disable plugin temporarily

all

Deactivate the Custom Script Integration plugin until patched version is available

Implement CSRF tokens manually

all

Add CSRF protection to plugin forms if you have development capabilities

🧯 If You Can't Patch

  • Remove the Custom Script Integration plugin completely
  • Implement web application firewall rules to block suspicious POST requests to plugin endpoints

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin > Plugins > Installed Plugins for Custom Script Integration version. If version is 2.1 or earlier, you are vulnerable.

Check Version:

wp plugin list --name=custom-script-integration --field=version

Verify Fix Applied:

After updating, verify the plugin version shows higher than 2.1 in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /wp-admin/admin-ajax.php or plugin-specific endpoints
  • Multiple failed authentication attempts followed by successful plugin modification requests

Network Indicators:

  • Unexpected JavaScript injection in plugin settings or page outputs
  • Cross-origin requests to plugin administration endpoints

SIEM Query:

source="wordpress" AND (uri_path="/wp-admin/admin-ajax.php" OR uri_path CONTAINS "custom-script-integration") AND http_method="POST" AND status_code=200

🔗 References

📤 Share & Export