CVE-2025-11379
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 · uneditedThe WebP Express plugin for WordPress is vulnerable to information exposure via config files in all versions up to, and including, 0.25.9. This is due to the plugin not properly randomizing the name of the config file to prevent direct access on NGINX. This makes it possible for unauthenticated attackers to extract configuration data.
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 confidenceThe WebP Express WordPress plugin (versions up to 0.25.9) exposes configuration files due to inadequate randomization of the config filename. Attackers can directly access these config files on NGINX servers to extract sensitive configuration data, including potentially database credentials or other settings.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WebP Express plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate WebP Express. Note the version number. Alternatively, check the plugin files in wp-content/plugins/webp-express/ for a version file or header.Affected if Installed version is 0.25.9 or lower
-
Confirm web server is NGINXCheck your server configuration or run a command such as 'nginx -v' or inspect the HTTP response headers for the server type.Affected if NGINX is the web server (this vulnerability specifically affects NGINX configurations)
-
Locate the WebP Express config directoryCheck the wp-content/webp-express/ directory (or custom configured path) for config files. Common paths include wp-content/wpc-configs/ or within the plugin's config folder.Affected if Config directory exists and contains .json or .php config files
-
Inspect config file naming patternList files in the config directory. Check if filenames appear predictable (e.g., sequential numbers, simple patterns) rather than cryptographically randomized.Affected if Config filenames follow a predictable, non-randomized pattern
-
Test direct web access to config filesAttempt to access config files directly via browser or curl, for example: https://yourdomain.com/wp-content/webp-express/config/<filename>. Check if the server serves the config file content.Affected if Config files are directly accessible via HTTP and return sensitive configuration data
You are affected if WebP Express plugin version is 0.25.9 or lower, NGINX is your web server, and config files are accessible via direct web requests.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to version 0.25.10 or later which properly randomizes config filenames. Additionally, configure NGINX to deny direct access to the config directory.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11379 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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