VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed Dec 10, 2016

Delete All Comments Vulnerabilities

Review known vulnerability records for the WordPress plugin Delete All Comments (`delete-all-comments`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2016-15033, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
1
Patch Coverage
100%
Last Updated
Jan 22, 2024
Related Security Guides

Use these guides while reviewing Delete All Comments fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Delete All Comments remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is delete-all-comments before acting on any CVE from this cluster.
2. Sort by Severity
Start with 1 high or critical record, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2016-15033 Critical
Remote Code Execution remediation for Delete All Comments

Affected range: Versions up to 2.0. Fixed version is not listed yet.

Priority CVE Quick Links

Fast paths into Delete All Comments CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2016-15033
Delete All Comments <= 2.0 - Arbitrary File Upload
 Remote Code Execution Versions up to 2.0 No patch listed CVSS 9.8
CVE-2016-15033 Critical No patch listed
CVE-2016-15033 Delete All Comments Remote Code Execution

Delete All Comments <= 2.0 - Arbitrary File Upload

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Delete All Comments so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
1 critical and 0 high severity findings.
Recent CVEs
CVE-2016-15033
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Delete All Comments

Sorted by latest disclosure date so newly published issues surface first.

Plugin Critical Patched: No CVE-2016-15033
CVE-2016-15033: Delete All Comments <= 2.0 - Arbitrary File Upload

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

Published
Dec 10, 2016
Patched Release
Not published
Affected Versions
Versions up to 2.0
Next Step
Open the full report for remediation notes and references.
Review CVE-2016-15033 fixed version details Open CVE Reference