CVE-2024-34435

4.3 MEDIUM

📋 TL;DR

This CVE describes a Missing Authorization vulnerability in the WordPress Aiomatic plugin that allows unauthorized users to perform actions intended only for authenticated users. It affects all versions up to 1.9.3. WordPress sites using this plugin are vulnerable to broken access control attacks.

💻 Affected Systems

Products:
  • WordPress Aiomatic (Automatic AI Content Writer) plugin
Versions: All versions up to and including 1.9.3
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Affects WordPress installations with the Aiomatic plugin installed and activated.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Unauthenticated attackers could modify plugin settings, generate unauthorized AI content, or potentially escalate privileges to compromise the WordPress site.

🟠

Likely Case

Unauthorized users can access administrative functions of the Aiomatic plugin, potentially modifying AI content generation settings or accessing restricted features.

🟢

If Mitigated

With proper authorization checks, only authenticated users with appropriate permissions can access plugin functionality.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Missing authorization vulnerabilities typically require minimal technical skill to exploit once the vulnerable endpoint is identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.9.4 or later

Vendor Advisory: https://patchstack.com/database/vulnerability/aiomatic-automatic-ai-content-writer/wordpress-aiomatic-plugin-1-9-3-broken-access-control-vulnerability

Restart Required: No

Instructions:

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

🔧 Temporary Workarounds

Disable Aiomatic Plugin

all

Temporarily disable the vulnerable plugin until patched

wp plugin deactivate aiomatic

Restrict Plugin Access via .htaccess

linux

Add access restrictions to plugin directories

# Add to .htaccess in wp-content/plugins/aiomatic/
Order Deny,Allow
Deny from all

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block unauthorized access to Aiomatic plugin endpoints
  • Monitor access logs for unauthorized requests to /wp-content/plugins/aiomatic/ paths

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for Aiomatic version. If version is 1.9.3 or lower, you are vulnerable.

Check Version:

wp plugin get aiomatic --field=version

Verify Fix Applied:

After updating, verify Aiomatic plugin shows version 1.9.4 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized POST/GET requests to /wp-content/plugins/aiomatic/ endpoints
  • 403/401 errors followed by successful 200 responses to same endpoints

Network Indicators:

  • Unusual traffic patterns to Aiomatic plugin endpoints from unauthenticated users

SIEM Query:

source="wordpress.log" AND (uri_path="/wp-content/plugins/aiomatic/" OR plugin="aiomatic") AND response_code=200 AND user="-"

🔗 References

📤 Share & Export