CVE-2024-7573

5.3 MEDIUM

📋 TL;DR

The Relevanssi Live Ajax Search WordPress plugin has an argument injection vulnerability that allows unauthenticated attackers to manipulate search queries. This can expose sensitive content like private posts or attachments. All WordPress sites using this plugin up to version 2.4 are affected.

💻 Affected Systems

Products:
  • Relevanssi Live Ajax Search WordPress Plugin
Versions: All versions up to and including 2.4
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: All WordPress installations with the vulnerable plugin are affected regardless of configuration.

⚠️ 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 extract sensitive private posts, draft content, or attachments that should not be publicly accessible, potentially exposing confidential information.

🟠

Likely Case

Information disclosure of non-public content that attackers can access through manipulated search queries.

🟢

If Mitigated

Limited exposure if proper access controls and input validation are already in place, but the vulnerability still exists at the plugin level.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

The vulnerability requires no authentication and manipulation of POST data is straightforward.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.4.1

Vendor Advisory: https://plugins.trac.wordpress.org/changeset/3135074/relevanssi-live-ajax-search

Restart Required: No

Instructions:

1. Log into WordPress admin panel
2. Navigate to Plugins → Installed Plugins
3. Find Relevanssi Live Ajax Search
4. Click 'Update Now' if available
5. Alternatively, download version 2.4.1+ from WordPress repository
6. Deactivate and delete old version, then upload new version

🔧 Temporary Workarounds

Disable the plugin

all

Temporarily deactivate the Relevanssi Live Ajax Search plugin until patched

wp plugin deactivate relevanssi-live-ajax-search

Restrict access to search endpoint

linux

Use web application firewall or .htaccess to restrict POST requests to the vulnerable endpoint

# Add to .htaccess:
<Files "admin-ajax.php">
    <IfModule mod_authz_core.c>
        Require all denied
    </IfModule>
    <IfModule !mod_authz_core.c>
        Order deny,allow
        Deny from all
    </IfModule>
</Files>

🧯 If You Can't Patch

  • Implement web application firewall rules to block suspicious POST requests to admin-ajax.php
  • Monitor logs for unusual search query patterns and implement rate limiting on search endpoints

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel → Plugins → Relevanssi Live Ajax Search version. If version is 2.4 or lower, you are vulnerable.

Check Version:

wp plugin get relevanssi-live-ajax-search --field=version

Verify Fix Applied:

Verify plugin version is 2.4.1 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /wp-admin/admin-ajax.php with manipulated search parameters
  • Multiple search requests with unusual query parameters from single IPs

Network Indicators:

  • POST requests to admin-ajax.php endpoint with unusual parameter values
  • Traffic spikes to search functionality

SIEM Query:

source="wordpress.log" AND "admin-ajax.php" AND "action=relevanssi_live_search" AND ("post_type" OR "post_status" OR unusual parameter patterns)

🔗 References

📤 Share & Export