Unauthenticated file upload via unchecked cache file type
Published Aug 1, 2025 · Updated Apr 8, 2026
Arbitrary file upload in BerqWP 2.2.42 and earlier allows remote attackers to place files on WordPress servers without authentication. The store_javascript_cache.php handler writes supplied cache files without validating their type, allowing executable content to reach server storage. No account is required; code execution requires the server to execute the uploaded file, while arbitrary file placement is the direct consequence.
Summary
What happened
Arbitrary file upload in BerqWP 2.2.42 and earlier allows remote attackers to place files on WordPress servers without authentication. The store_javascript_cache.php handler writes supplied cache files without validating their type, allowing executable content to reach server storage. No account is required; code execution requires the server to execute the uploaded file, while arbitrary file placement is the direct consequence.
The record
- CVE
- CVE-2025-7443
- Published
- Aug 1, 2025
- Updated
- Apr 8, 2026
- Vendor
- Berqier Ltd
- Product
- BerqWP
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.2.42
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo