Skip to content
Laskyr

Plugins · tiny-compress-images · data as of 2026-11-04

Is TinyPNG Image Optimization safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.8.1)

As of 2026-11-04. 2 issues are on record for older versions; version 3.6.14 or newer fixes all of them that state a fix.

Latest version
3.8.1
Last updated
2026-10-13
Active installs
100,000+
Known issues on record
2
Unpatched in latest
0
Tested up to WP
7.1.4

Speed up your website. Optimize your JPEG, PNG, and WebP images automatically with TinyPNG. — by TinyPNG

What to do

  1. Update to the latest version (3.8.1). Anything older than 3.6.14 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get tiny-compress-images --field=version shows what you run; wp plugin update tiny-compress-images updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 8.1 CVE-2026-7311 · published 2026-07-02

Arbitrary file deletion in TinyPNG Image Optimization (3.6.13 and older)

Affected
3.6.13 and older
Fixed in
3.6.14 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

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.

NVD CVE-2026-7311Wordfence advisoryCode change (fix)Plugin source

medium 5.4 CVE-2024-47635 · published 2024-10-05

Cross-site request forgery (CSRF) in TinyPNG Image Optimization (3.4.3 and older)

Affected
3.4.3 and older
Fixed in
3.4.4
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in TinyPNG TinyPNG tiny-compress-images allows Cross Site Request Forgery.This issue affects TinyPNG: from n/a through <= 3.4.3.

NVD CVE-2024-47635Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
TinyPNG Image Optimization vulnerability status badge
<a href="https://laskyr.com/plugins/tiny-compress-images"><img src="https://laskyr.com/plugins/tiny-compress-images/badge.svg" alt="TinyPNG Image Optimization vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit