CVE-2025-6206

7.5 HIGH

📋 TL;DR

This vulnerability allows authenticated WordPress users with Subscriber-level access or higher to upload arbitrary files to the server due to missing file type validation in the Aiomatic plugin. Attackers can potentially achieve remote code execution if they upload malicious files like PHP shells. The vulnerability affects all Aiomatic plugin versions up to and including 2.5.0.

💻 Affected Systems

Products:
  • Aiomatic - Automatic AI Content Writer & Editor, GPT-3 & GPT-4, ChatGPT ChatBot & AI Toolkit WordPress plugin
Versions: All versions up to and including 2.5.0
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires: 1) WordPress installation with Aiomatic plugin, 2) Authenticated user with Subscriber role or higher, 3) Any value in Stability.AI API key field (can be arbitrary)

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete server compromise, data theft, malware deployment, or website defacement.

🟠

Likely Case

Unauthorized file upload leading to backdoor installation, privilege escalation, or data exfiltration.

🟢

If Mitigated

Limited impact if file execution is prevented through server configuration or web application firewalls.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authenticated access but only at Subscriber level, which is easy to obtain through registration on many sites. The arbitrary API key requirement is trivial to bypass.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.5.1 or later

Vendor Advisory: https://codecanyon.net/item/aiomatic-automatic-ai-content-writer/38877369#item-description__changelog

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 2.5.1+ from CodeCanyon and manually update.

🔧 Temporary Workarounds

Disable plugin temporarily

all

Deactivate the Aiomatic plugin until patched

wp plugin deactivate aiomatic

Restrict file uploads via .htaccess

linux

Block execution of uploaded files in wp-content/uploads directory

Add to .htaccess in wp-content/uploads: <Files *.php> deny from all </Files>

🧯 If You Can't Patch

  • Remove Subscriber role registration capability or implement strong user approval process
  • Implement web application firewall (WAF) rules to block suspicious file uploads

🔍 How to Verify

Check if Vulnerable:

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

Check Version:

wp plugin get aiomatic --field=version

Verify Fix Applied:

Confirm Aiomatic plugin version is 2.5.1 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual file uploads to wp-content/uploads via /wp-admin/admin-ajax.php with action=aiomatic_image_editor_ajax_submit
  • Multiple failed login attempts followed by successful Subscriber login

Network Indicators:

  • POST requests to /wp-admin/admin-ajax.php with file uploads containing executable extensions

SIEM Query:

source="web_logs" AND uri="/wp-admin/admin-ajax.php" AND post_data CONTAINS "aiomatic_image_editor_ajax_submit" AND (post_data CONTAINS ".php" OR post_data CONTAINS ".exe" OR post_data CONTAINS ".sh")

🔗 References

📤 Share & Export