Smush Image Compression And OptimizationWordPress extension · Wpmudev
CVE-2017-15079
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 Smush Image Compression and Optimization plugin before 2.7.6 for WordPress allows directory traversal.
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 confidenceThe Smush Image Compression and Optimization WordPress plugin before version 2.7.6 contains a directory traversal vulnerability (CWE-22) that allows attackers to access files outside the web root directory. This could enable unauthorized reading of sensitive system files.
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
Smush Image Compression And OptimizationWordPress extension
<= 2.7.5CVSS 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.0/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 Smush plugin installation and versionNavigate to WordPress admin > Plugins and locate 'Smush Image Compression and Optimization', or check the plugin files in /wp-content/plugins/smush/ for the main PHP file to read the version headerAffected if The plugin is installed with version 2.7.5 or lower
-
Inspect plugin directory for version fileAccess the plugin directory via FTP or file manager, open the primary plugin PHP file (typically class-smush.php or wp-smush.php) and locate the 'Version:' header in the plugin comment blockAffected if The version declared in the plugin header is 2.7.5 or lower
-
Check for unauthorized file access indicatorsReview web server access logs for requests to the Smush plugin endpoint containing directory traversal patterns (such as '../' or absolute paths outside the wp-content directory)Affected if Log entries show requests to smush-related URLs with traversal sequences attempting to access files outside the WordPress installation
-
Review plugin files for tamperingCompare hash of core Smush plugin files against known clean versions, or manually inspect the wp-smush.php and related files for unexpected code changesAffected if Plugin files contain modified code or new files that were not part of the original plugin distribution
The environment is affected if the Smush Image Compression and Optimization plugin version is 2.7.5 or lower, as this version contains the directory traversal vulnerability that could allow unauthorized file access.
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 dataUpdate the Smush plugin to version 2.7.6 or later. If immediate update is not possible, disable the plugin until patched.
Fix this in Smush Image Compression And Optimization
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15079 — 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-2017-15079 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