CVE-2024-4474

4.3 MEDIUM

📋 TL;DR

The WP Logs Book WordPress plugin through version 1.0.1 lacks CSRF protection on its settings update functionality. This allows attackers to trick logged-in administrators into unknowingly changing plugin settings via malicious links or forms. Only WordPress sites using this specific plugin are affected.

💻 Affected Systems

Products:
  • WP Logs Book WordPress Plugin
Versions: through 1.0.1
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with the plugin active and an administrator logged in.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker could modify plugin settings to enable logging of sensitive data, disable security features, or redirect logs to attacker-controlled locations, potentially leading to data exposure or further compromise.

🟠

Likely Case

Attackers could change logging configurations to reduce visibility, disable audit trails, or modify log retention settings to hide malicious activity.

🟢

If Mitigated

With proper CSRF protections in place, only authenticated administrators with explicit intent can modify settings, preventing unauthorized changes.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: LOW

🎯 Exploit Status

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

Exploitation requires social engineering to trick an administrator into clicking a malicious link while authenticated.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.0.2 or later

Vendor Advisory: https://wpscan.com/vulnerability/71954c60-6a5b-4cac-9920-6d9b787ead9c/

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find WP Logs Book plugin. 4. Click 'Update Now' if update available. 5. Alternatively, delete and reinstall latest version from WordPress repository.

🔧 Temporary Workarounds

Temporary Plugin Deactivation

all

Disable the vulnerable plugin until patched

wp plugin deactivate wp-logs-book

CSRF Protection via .htaccess

linux

Add basic CSRF protection headers at web server level

Header set X-Frame-Options "SAMEORIGIN"
Header set Content-Security-Policy "frame-ancestors 'self'"

🧯 If You Can't Patch

  • Remove WP Logs Book plugin entirely and use alternative logging solutions
  • Implement strict access controls limiting admin panel access to trusted networks only

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Installed Plugins for WP Logs Book version 1.0.1 or earlier

Check Version:

wp plugin get wp-logs-book --field=version

Verify Fix Applied:

Verify plugin version is 1.0.2 or later in WordPress admin plugins page

📡 Detection & Monitoring

Log Indicators:

  • Unexpected changes to wp_logs_book settings in WordPress database
  • Admin user settings modifications without corresponding admin panel access logs

Network Indicators:

  • POST requests to /wp-admin/admin-post.php with wp_logs_book parameters from unexpected referrers

SIEM Query:

source="wordpress" AND (uri_path="/wp-admin/admin-post.php" AND query="*wp_logs_book*" AND NOT referrer_domain="*yourdomain.com*")

🔗 References

📤 Share & Export