Image OptimizerWordPress extension · Ewww
CVE-2023-40600
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Exactly WWW EWWW Image Optimizer. It works only when debug.log is turned on.This issue affects EWWW Image Optimizer: from n/a through 7.2.0.
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 · moderate confidenceAn information disclosure vulnerability in the EWWW Image Optimizer WordPress plugin allows unauthorized actors to access sensitive information through the debug.log file when debugging is enabled. The flaw exists in versions through 7.2.0 and requires debug.log to be actively turned on for exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Image OptimizerWordPress extension
< 7.2.1CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 EWWW Image Optimizer is installedIn WordPress admin, go to Plugins > Installed Plugins and find EWWW Image Optimizer, or check the plugin files in /wp-content/plugins/ewww-image-optimizer/ for the main PHP file containing the version numberAffected if Plugin is installed and version is less than 7.2.1
-
Check WordPress debug configuration in wp-config.phpOpen wp-config.php in the WordPress root directory and search for WP_DEBUG and WP_DEBUG_LOG constantsAffected if WP_DEBUG is set to true OR WP_DEBUG_LOG is set to true
-
Locate the debug.log fileLook for debug.log in the wp-content directory or the directory specified by WP_DEBUG_LOG constantAffected if debug.log file exists and is readable by web server user
-
Verify debug.log contains sensitive informationExamine the debug.log file content for potential sensitive data such as file paths, database credentials, or other WordPress internals that could be exposedAffected if debug.log exists and contains sensitive information accessible without authentication
User is affected if EWWW Image Optimizer version is below 7.2.1 AND WordPress debug logging (WP_DEBUG or WP_DEBUG_LOG) is enabled, creating an accessible debug.log file.
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.
dbcve · scoped7.2.1
Disable debug.log in the WordPress wp-config.php file (set WP_DEBUG to false) or upgrade to a patched version of EWWW Image Optimizer once released.
7.2.1
- Update EWWW Image Optimizer plugin to version 7.2.1 or later
- Verify the update was successful by checking the plugin version in WordPress admin
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Image Optimizer
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40600 — 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-2023-40600 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