CVE-2024-6846

5.3 MEDIUM

📋 TL;DR

The Chatbot with ChatGPT WordPress plugin before version 2.4.5 has improper access control on certain REST API endpoints. This allows unauthenticated attackers to delete error logs and chat logs, potentially covering their tracks after other attacks. All WordPress sites using vulnerable versions of this plugin are affected.

💻 Affected Systems

Products:
  • Chatbot with ChatGPT WordPress plugin
Versions: All versions before 2.4.5
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with the vulnerable plugin activated. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers purge logs to hide evidence of successful attacks like data exfiltration or privilege escalation, making incident response and forensic investigation significantly more difficult.

🟠

Likely Case

Attackers delete chat logs containing sensitive user conversations or remove error logs that could reveal system weaknesses, disrupting operational monitoring.

🟢

If Mitigated

With proper logging redundancy and external log aggregation, the impact is limited to temporary loss of plugin-specific logs without affecting overall security monitoring.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

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

Simple HTTP requests to specific REST endpoints can trigger the vulnerability without authentication. No special tools or skills required.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.4.5

Vendor Advisory: https://wpscan.com/vulnerability/d48fdab3-669c-4870-a2f9-6c39a7c25fd8/

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Chatbot with ChatGPT' plugin. 4. Click 'Update Now' if update is available. 5. Alternatively, download version 2.4.5+ from WordPress repository and manually update.

🔧 Temporary Workarounds

Disable vulnerable REST endpoints

all

Block access to the specific REST API routes that allow log purging

Add to .htaccess: RewriteRule ^wp-json/chatbot-with-chatgpt/v1/purge-logs - [F,L]
Add to nginx config: location ~* ^/wp-json/chatbot-with-chatgpt/v1/purge-logs { return 403; }

Deactivate plugin

all

Temporarily disable the plugin until patched

wp plugin deactivate chatbot-with-chatgpt

🧯 If You Can't Patch

  • Implement external log aggregation to capture logs before they can be purged
  • Restrict access to WordPress REST API endpoints using web application firewall rules

🔍 How to Verify

Check if Vulnerable:

Check plugin version in WordPress admin panel under Plugins → Installed Plugins. If version is below 2.4.5, the site is vulnerable.

Check Version:

wp plugin get chatbot-with-chatgpt --field=version

Verify Fix Applied:

Confirm plugin version is 2.4.5 or higher. Test by attempting to access /wp-json/chatbot-with-chatgpt/v1/purge-logs endpoint without authentication - should return 403 or 404.

📡 Detection & Monitoring

Log Indicators:

  • HTTP 200 responses to POST /wp-json/chatbot-with-chatgpt/v1/purge-logs from unauthenticated IPs
  • Sudden disappearance of plugin-specific log entries

Network Indicators:

  • Unusual volume of requests to WordPress REST API endpoints from external IPs
  • POST requests to /wp-json/chatbot-with-chatgpt/v1/* without authentication headers

SIEM Query:

source="wordpress.log" AND (uri_path="/wp-json/chatbot-with-chatgpt/v1/purge-logs" OR uri_path="/wp-json/chatbot-with-chatgpt/v1/delete-logs") AND http_status=200 AND NOT user_agent="WordPress/*"

🔗 References

📤 Share & Export