LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36505: Delete All Comments Easily <= 1.3 - All Comments Deletion via CSRF

The Delete All Comments Easily WordPress plugin through 1.3 is lacking Cross-Site Request Forgery (CSRF) checks, which could result in an unauthenticated attacker making a logged in admin delete all comments from the blog.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This WordPress plugin vulnerability lets an attacker trick a logged-in administrator into deleting all blog comments. It is a CSRF issue, so the attacker needs the admin to interact with attacker-controlled content while authenticated. The documented impact is comment data loss, not server takeover.

Executive priority

Treat this as a targeted data-integrity risk for affected WordPress sites. It is not documented as remote code execution, but it can erase community or customer comment history if an admin is successfully targeted.

Technical view

CVE-2020-36505 affects Delete All Comments Easily WordPress plugin through version 1.3. Missing CSRF checks around the comment deletion action can allow an unauthenticated attacker to cause a logged-in admin browser to submit a destructive request. The weakness is CWE-352. No CVSS score or fixed version is provided in the source bundle.

Likely exposure

Exposure is limited to WordPress sites with Delete All Comments Easily installed at version 1.3 or earlier, especially sites where administrators remain logged in and can be lured to attacker-controlled pages.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. A public write-up is referenced, but the provided evidence supports vulnerability existence, not current exploitation in the wild.

Researcher notes

Evidence identifies missing CSRF checks and destructive comment deletion through admin interaction. Sources do not provide CVSS, a fixed release, exploit-in-the-wild confirmation, or broader affected CPE data. Avoid assuming impact beyond comment deletion.

Mitigation direction

  • Inventory WordPress sites for Delete All Comments Easily versions through 1.3.
  • Check vendor or plugin guidance for a fixed version or official mitigation.
  • Disable or remove the plugin if no safe vendor guidance is available.
  • Back up comment data before making plugin or site changes.
  • Limit WordPress admin sessions to trusted devices and routine workflows.

Validation and detection

  • Confirm whether Delete All Comments Easily is installed on each WordPress site.
  • Record installed plugin versions and compare against affected version 1.3 or earlier.
  • Review whether comment deletion requires CSRF protection in the deployed plugin.
  • Check recent admin activity for unexpected bulk comment deletion.
  • Verify comment backups can restore deleted content if needed.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-36505 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownDelete All Comments Easily1.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.