CVE-2016-15033: The Delete All Comments plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type

Q: How do I fix CVE-2016-15033?

delete all comments: upgrade to newer than 2.0. Exact commands for each OS are on this page.

Q: Is CVE-2016-15033 being exploited?

CVE-2016-15033 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-15033 affect?

CVE-2016-15033 affects delete all comments. Severity is critical (CVSS 9.8). The Delete All Comments plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the via the delete-all-comments.php file in versions up to, and including, 2.0. This makes it possible for unauthent

Q: How urgent is CVE-2016-15033?

Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2016-15033 is a critical-severity flaw (CVSS 9.8) affecting delete all comments. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Delete All Comments plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the via the delete-all-comments.php file in versions up to, and including, 2.0. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.3% (top 17%)
CISA exploited list	No
Weakness	CWE-434
Published	2023-06-07
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: delete all comments project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-06-07 02:15 UTCPublished CVE record published
2026-06-17 00:41 UTCUpdated Record last modified

delete all comments project delete all comments UPGRADE

Affected: <= 2.0

Fixed in: newer than 2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy delete-all-comments || rpm -q delete-all-comments || delete-all-comments --version

2. UPGRADE to newer than 2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade delete-all-comments

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade delete-all-comments

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-15033?

delete all comments: upgrade to newer than 2.0. Exact commands for each OS are on this page.

Is CVE-2016-15033 being exploited?

CVE-2016-15033 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-15033 affect?

CVE-2016-15033 affects delete all comments. Severity is critical (CVSS 9.8). The Delete All Comments plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the via the delete-all-comments.php file in versions up to, and including, 2.0. This makes it possible for unauthent

How urgent is CVE-2016-15033?

Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs