CVE-2026-7311
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 TinyPNG – JPEG, PNG & WebP image compression plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_converted_image_size function in all versions up to, and including, 3.6.13. This makes it possible for authenticated attackers, with author-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). An attacker can exploit this by injecting an arbitrary server file path into the 'convert.path' field of the 'tiny_compress_images' post meta on an attachment they own, then triggering attachment deletion to invoke the vulnerable code path.
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 TinyPNG WordPress plugin has an arbitrary file deletion vulnerability in the delete_converted_image_size function due to insufficient path validation. Authenticated attackers with author-level access can inject an arbitrary file path into the 'convert.path' field of the 'tiny_compress_images' post meta on their own attachments, then trigger attachment deletion to delete any file on the server, potentially leading to RCE by deleting wp-config.php.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify TinyPNG plugin is installedCheck the WordPress plugins directory or admin panel for the TinyPNG plugin. Look for files in wp-content/plugins/tiny-compress-images/ or check via wp-cli: wp plugin list --name='tiny-compress-images'Affected if The plugin is installed and active on the WordPress site
-
Determine installed plugin versionReview the plugin header in tiny-compress-images/tiny-compress-images.php or check via wp-cli: wp plugin get tiny-compress-images --format=jsonAffected if The version is 3.6.13 or lower (versions beyond 3.6.13 contain the fix)
-
Identify users with author-level or higher accessIn WordPress admin, go to Users > All Users and review roles. Check for any untrusted or unexpected accounts with author, editor, or administrator roles. Use wp-cli: wp user list --role=author --format=countAffected if There are author-level users who should not have write access to their own post metadata, or the site has untrusted accounts at this access level
-
Inspect post meta for suspicious convert.path valuesQuery the wp_postmeta table for tiny_compress_images meta_value entries containing unusual paths. Use SQL: SELECT post_id, meta_value FROM wp_postmeta WHERE meta_key = 'tiny_compress_images' AND meta_value LIKE '%..%' OR meta_value LIKE '%/etc/%' OR meta_value LIKE '%wp-config.php%'Affected if Any tiny_compress_images meta contains path traversal sequences or references to sensitive system files outside the uploads directory
You are affected if the TinyPNG plugin version is 3.6.13 or lower AND there are author-level or higher users on the site who could inject arbitrary paths into tiny_compress_images post meta to trigger arbitrary file deletion.
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 plugin to version 3.6.14 or later once available. As an interim measure, restrict user permissions to author-level and below until the patch is applied.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7311 — 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-2026-7311 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