CVE-2024-56015

7.1 HIGH

📋 TL;DR

This CSRF vulnerability in the John Godley Tidy Up WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions, which can lead to reflected cross-site scripting (XSS). The vulnerability affects all WordPress sites using Tidy Up plugin versions up to 1.3, potentially compromising site security and user data.

💻 Affected Systems

Products:
  • John Godley Tidy Up WordPress Plugin
Versions: n/a through 1.3
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires the Tidy Up plugin to be installed and activated on a WordPress site. The vulnerability affects the plugin's admin interface functionality.

⚠️ 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 malicious scripts that steal administrator credentials, deface websites, or install backdoors, leading to complete site compromise and data theft.

🟠

Likely Case

Attackers create fake admin actions that inject malicious JavaScript, potentially stealing session cookies or redirecting users to phishing sites.

🟢

If Mitigated

With proper CSRF protections and content security policies, the attack surface is significantly reduced, though some risk remains if users are tricked into clicking malicious links.

🌐 Internet-Facing: HIGH - WordPress sites are typically internet-facing, and CSRF attacks can be delivered via phishing emails or malicious websites.
🏢 Internal Only: LOW - The vulnerability requires interaction with the WordPress admin interface, which is typically not exposed internally without authentication.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires tricking an authenticated administrator into clicking a malicious link or visiting a compromised page. The CSRF leads to reflected XSS, making it relatively straightforward for attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.4 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/tidy-up/vulnerability/wordpress-tidy-up-plugin-1-3-csrf-to-reflected-cross-site-scripting-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Tidy Up' and check if update is available. 4. Click 'Update Now' to upgrade to version 1.4 or later. 5. Verify the plugin is updated successfully.

🔧 Temporary Workarounds

Disable Tidy Up Plugin

all

Temporarily deactivate the vulnerable plugin until patched

wp plugin deactivate tidy-up

Implement CSRF Protection Headers

all

Add security headers to WordPress to help mitigate CSRF attacks

Add to .htaccess: Header set X-Frame-Options "SAMEORIGIN"
Add to wp-config.php: define('FORCE_SSL_ADMIN', true);

🧯 If You Can't Patch

  • Restrict admin access to trusted IP addresses only using firewall rules or .htaccess restrictions
  • Implement strong content security policies (CSP) to prevent XSS execution even if CSRF succeeds

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Installed Plugins, look for Tidy Up version. If version is 1.3 or earlier, you are vulnerable.

Check Version:

wp plugin get tidy-up --field=version

Verify Fix Applied:

After updating, verify Tidy Up plugin shows version 1.4 or later in WordPress admin plugins list.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to Tidy Up admin endpoints
  • Multiple failed CSRF token validations in WordPress logs
  • Unexpected script injections in plugin settings

Network Indicators:

  • HTTP requests containing malicious script payloads in parameters
  • Cross-origin requests to Tidy Up admin endpoints

SIEM Query:

source="wordpress.log" AND ("tidy-up" OR "CSRF token") AND ("failed" OR "invalid" OR "malicious")

🔗 References

📤 Share & Export