CVE-2024-54391

7.1 HIGH

📋 TL;DR

A Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Filter plugin allows attackers to perform stored cross-site scripting (XSS) attacks. This affects WordPress sites using the WordPress Filter plugin version 1.4.1 and earlier. Attackers can trick authenticated administrators into executing malicious actions that inject persistent scripts.

💻 Affected Systems

Products:
  • WordPress Filter plugin
Versions: n/a through 1.4.1
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with the vulnerable plugin enabled and administrator access to trigger the CSRF.

⚠️ 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 JavaScript that steals administrator credentials, defaces websites, or installs backdoors when administrators view affected pages.

🟠

Likely Case

Attackers create phishing campaigns targeting administrators to inject malicious scripts that redirect users or steal session cookies.

🟢

If Mitigated

With proper CSRF protections and input validation, the attack would fail or have minimal impact.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires tricking an authenticated administrator into clicking a malicious link or visiting a crafted page.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.4.2 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/wordpress-filter/vulnerability/wordpress-wordpress-filter-plugin-1-4-1-csrf-to-stored-xss-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'WordPress Filter' plugin. 4. Click 'Update Now' if available, or manually update to version 1.4.2+. 5. Verify the plugin is active and functioning.

🔧 Temporary Workarounds

Disable WordPress Filter Plugin

all

Temporarily deactivate the vulnerable plugin until patched.

wp plugin deactivate wordpress-filter

Implement CSRF Tokens

all

Add CSRF protection to WordPress admin forms if custom development is possible.

🧯 If You Can't Patch

  • Disable the WordPress Filter plugin immediately to prevent exploitation.
  • Implement web application firewall (WAF) rules to block CSRF attempts and XSS payloads.

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin > Plugins > Installed Plugins for 'WordPress Filter' version 1.4.1 or lower.

Check Version:

wp plugin get wordpress-filter --field=version

Verify Fix Applied:

Confirm the plugin version is 1.4.2 or higher in the WordPress plugins list.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to WordPress admin endpoints related to the filter plugin
  • JavaScript injection patterns in plugin settings or content

Network Indicators:

  • CSRF attack patterns with malicious payloads targeting /wp-admin/
  • Unexpected redirects or script loads from compromised pages

SIEM Query:

source="wordpress" AND (uri_path="/wp-admin/admin-ajax.php" OR uri_path CONTAINS "wordpress-filter") AND (http_method="POST" AND user_agent CONTAINS "malicious")

🔗 References

📤 Share & Export