highCVE-2026-7311

TinyPNG <= 3.6.13 - Authenticated (Author+) Arbitrary File Deletion via 'convert.path' in 'tiny_compress_images' Post Meta

Q: What is affected by CVE-2026-7311?

TinyPNG – JPEG, PNG & WebP image compression versions listed as affected should be reviewed: *-3.6.13.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

The 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.

ProductTinyPNG – JPEG, PNG & WebP image compression

CVSS8.1

EPSS0.0067

UpdatedJuly 13, 2026

Quick answer

TinyPNG – JPEG, PNG & WebP image compression should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

*-3.6.13

Fixed versions

3.6.14

How to fix it

TinyPNG – JPEG, PNG & WebP image compression is affected by CVE-2026-7311, a arbitrary file deletion and possible site compromise issue in versions *-3.6.13. Prioritize exposed production sites and users with elevated permissions first. The recommended remediation is to update to version 3.6.14 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable workflow, and monitor logs until the vendor-supported fix is in place.

Inventory every WordPress site that uses TinyPNG – JPEG, PNG & WebP image compression, including production, staging, multisite, customer, and managed environments.
Confirm the installed plugin or theme version and compare it with versions *-3.6.13 from the linked advisory.
Apply the remediation: update to version 3.6.14 or a newer vendor-supported patched release.
If the update cannot be applied immediately, disable TinyPNG – JPEG, PNG & WebP image compression, remove unused roles that can reach the vulnerable feature, and restrict the affected admin, REST, shortcode, upload, comment, booking, or ecommerce workflow.
Review application, web server, security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-7311.
Rotate administrator sessions, API keys, webhook secrets, database credentials, and integration tokens if logs or file/content review suggest compromise.
Clear application, object, page, CDN, and browser caches after remediation so vulnerable assets, stored payloads, or stale responses are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm TinyPNG – JPEG, PNG & WebP image compression is no longer running versions *-3.6.13 and record the patched or mitigated version in the remediation ticket.
Verify unauthenticated, subscriber, contributor, author, shop manager, donor, booking, or custom-role users can no longer trigger the affected action.
Review logs before and after the fix for exploitation attempts, unexpected content changes, suspicious admin actions, or database/file access.
Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
Document the advisory link, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.

Related categories

WordPress PHP Remote Code Execution Arbitrary File Write File Deletion

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-7311?

TinyPNG – JPEG, PNG & WebP image compression versions listed as affected should be reviewed: *-3.6.13.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.