dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-7443

HIGH · 8.1 CVSS v3.1 Published 2025-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The BerqWP – Automated All-In-One Page Speed Optimization for Core Web Vitals, Cache, CDN, Images, CSS, and JavaScript plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation via the store_javascript_cache.php file in all versions up to, and including, 2.2.42. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The BerqWP WordPress plugin is vulnerable to arbitrary file uploads due to missing file type validation in the store_javascript_cache.php file. Unauthenticated attackers can upload arbitrary files to the server, potentially achieving remote code execution. All versions up to and including 2.2.42 are affected.

MitigationUpdate the BerqWP plugin to version 2.2.43 or later. Additionally, audit the server for any malicious files that may have been uploaded and consider resetting credentials as a precaution given the RCE possibility.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify BerqWP plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'BerqWP - Automated WordPress Cache Plugin' in the list of installed plugins.
    Affected if The BerqWP plugin appears in the installed plugins list.
  2. Determine the installed BerqWP version
    In the WordPress admin, go to Plugins > Installed Plugins and locate BerqWP. The version number is displayed below the plugin name.
    Affected if The displayed version is 2.2.42 or any version lower than 2.2.43.
  3. Check if the vulnerable file exists
    Access the WordPress site files via FTP, file manager, or SSH. Navigate to /wp-content/plugins/berqwp/includes/ and look for the file store_javascript_cache.php.
    Affected if The file store_javascript_cache.php exists in the includes folder.
  4. Inspect web server access logs for exploit attempts
    Review your web server access logs (Apache, Nginx, or LiteSpeed) for POST requests to /wp-content/plugins/berqwp/includes/store_javascript_cache.php from unauthenticated IP addresses.
    Affected if There are POST requests to store_javascript_cache.php from unknown or unauthorized IP addresses, especially if they contain file upload patterns or suspicious content.
  5. Scan for recently uploaded suspicious files
    Search the /wp-content/uploads/ directory and other writable directories for executable files (.php, .phtml, .exe) that were created recently, especially around the time the vulnerability became known or after suspicious POST requests.
    Affected if Unexpected PHP files or other executable scripts are found in upload directories that were not deliberately uploaded by an administrator.

A user is affected if the BerqWP plugin is installed with version 2.2.42 or lower, or if the vulnerable store_javascript_cache.php file exists and shows signs of unauthorized access in logs or unexpected files in upload directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the BerqWP plugin to version 2.2.43 or later. Additionally, audit the server for any malicious files that may have been uploaded and consider resetting credentials as a precaution given the RCE possibility.

Recommended fix Moderate confidence

BerqWP version 2.2.43 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the BerqWP plugin
  4. Check the current version installed (should be 2.2.42 or below)
  5. Update the plugin to the latest available version (2.2.43 or later)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7443 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data