Skip to content
major vulnerability· requires attention

Widely used WordPress plugin; authenticated file deletion can disrupt numerous sites and lead to RCE.

Web

CVE-2026-7311

8.1
High
EPSS 1%Patch availableJul 3, 2026

Authenticated user can delete arbitrary server files via TinyPNG WordPress plugin.

common questions

Is CVE-2026-7311 being exploited?

Not confirmed. CVE-2026-7311 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.0% probability of exploitation in the next 30 days.

How severe is CVE-2026-7311?

CVE-2026-7311 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-7311?

Yes. A fix has been recorded for CVE-2026-7311. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-7311 affect?

CVE-2026-7311 affects TinyPNG WordPress plugin <= 3.6.13, WordPress sites using the plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-7311?

Update to latest plugin (>=3.6.14)

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TinyPNG WordPress plugin <= 3.6.13WordPress sites using the plugin
impact

Allows author+ attackers to delete arbitrary files; could enable remote code execution if a critical file is removed.

action required

Immediate action required

affected versions
tinypng TinyPNG – JPEG, PNG & WebP image compression
  • affected<= 3.6.13

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free