EUVD-2026-11747Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious GET request with valid HMAC key
-
DeliveryEmbed URL in image tag or resource
-
ExploitVictim visits page with embedded resource
-
Executiondeletecomments action executes
-
ImpactAll comments for target email deleted
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | wpDiscuz plugin before version 7.6.47 installed and active; attacker must obtain valid HMAC key; victim must visit attacker-controlled page or page with embedded malicious resource; requires user interaction (UI:R) to trigger the request. |
| Impact | Severity: High (8.1/10.0) No EPSS data available yet HIGH RISK: Remotely exploitable without authentication — internet-facing instances are directly vulnerable Patch is available — prioritize updating to the fixed version |
| Exploit ScenarioDerived | An attacker can exploit this vulnerability remotely, but requires a victim to interact with malicious content (e.g., visiting a crafted web page or clicking a link). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 13, 2026
High severity vulnerability in wpDiscuz (WordPress plugin). wpDiscuz before 7.6.47 contains a cross-site request forgery vulnerability that allows attackers to delete all comments associated with an email address by crafting a malicious GET request with a valid HMAC key. Attackers can embed the deletecomments action URL in image tags or other resources to trigger permanent deletion of comments without user confirmation or POST-based CSRF protection.
RemediationAI
Patches available:
- https://wordpress.org/plugins/wpdiscuz/#developers
Update to the latest patched version as soon as possible.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Vulnerability Type: Cross-Site Request Forgery (CSRF) (CWE-352) CVSS 3.1: 8.1/10.0 — Attack Vector: Network | Complexity: Low | Privileges Required: None | User Interaction: Required Attack Techniques: Csrf Source: VulnCheck CSRF allows attackers to trick authenticated users into performing unintended actions by embedding malicious requests in web pages.
Know when Wpdiscuz gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
wpDiscuz before 7.6.47 contains a cross-site request forgery vulnerability that allows attackers to delete all comments associated with an email address by crafting a malicious GET request with a valid HMAC key. Attackers can embed the deletecomments action URL in image tags or other resources to trigger permanent deletion of comments without user confirmation or POST-based CSRF protection.
Executive ViewAI
A high-severity vulnerability in the wpDiscuz WordPress plugin enables attackers to permanently delete all user comments through malicious web requests, potentially causing data loss and reputational damage. Any organization using wpDiscuz versions before 7.6.47 faces immediate risk of comment manipulation and destruction without user consent.
Apply vendor patch. If immediate patching is not feasible: (1) Disable wpDiscuz plugin temporarily; (2) Implement Web Application Firewall rules to block GET requests containing 'deletecomments' action parameters; (3) Restrict plugin functionality to authenticated users only via access controls; (4) Enable detailed comment activity logging to detect unauthorized deletion attempts.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
Related Vulnerabilities in wpDiscuz Multiple Security Vulnerabilities
View all 14A Remote Code Execution vulnerability exists in the gVectors wpDiscuz plugin 7.0 through 7.0.4 for WordPress, which allo
A SQL injection issue in the gVectors wpDiscuz plugin 5.3.5 and earlier for WordPress allows remote attackers to execute
The Comments - wpDiscuz plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including
Cross-Site Request Forgery (CSRF) vulnerability in gVectors Team Comments - wpDiscuz plugin <= 7.6.11 versions. Rated hi
Auth. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch
The Comments - wpDiscuz WordPress plugin through 7.3.0 does not properly sanitise or escape the Follow and Unfollow mess
The wpDiscuz WordPress plugin before 7.3.4 does check for CSRF when adding, editing and deleting comments, which could a
Sensitive information disclosure discovered in wpDiscuz WordPress plugin (versions <= 7.3.11). Rated high severity (CVSS
GitHub PoC
Exploit-DB