dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2026-22202

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 7.6.47 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

wpDiscuz before 7.6.47 contains a CSRF vulnerability allowing attackers to delete all comments associated with an email address via crafted GET requests using a valid HMAC key. The attack can be embedded in image tags or other external resources, triggering permanent comment deletion without user confirmation or POST-based CSRF protection.

MitigationUpgrade wpDiscuz to version 7.6.47 or later, which includes proper CSRF protection. Until then, consider disabling comment deletion functionality or implementing additional request validation at the WAF level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WpdiscuzWordPress extension
Affected:< 7.6.47

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify wpDiscuz plugin is installed
    Check your WordPress plugins directory or WordPress admin panel for the wpDiscuz plugin presence
    Affected if wpDiscuz is installed and active on the site
  2. Determine installed wpDiscuz version
    Check the plugin version in WordPress admin under Plugins > wpDiscuz, or inspect the main plugin file header for the Version field
    Affected if Version is less than 7.6.47 (e.g., 7.6.46, 7.6.45, etc.)
  3. Identify comment deletion endpoint exposure
    Examine network requests when using the comment deletion feature; look for GET-based endpoints that accept an email parameter and HMAC signature
    Affected if GET requests can trigger comment deletion without requiring POST method or user confirmation
  4. Check for HMAC-based deletion mechanism
    Review plugin code or HTTP traffic for HMAC key usage in comment deletion requests; the vulnerability requires a valid HMAC to be used
    Affected if The deletion function accepts and processes HMAC-signed GET requests to delete comments by email address
  5. Confirm lack of CSRF token validation
    Test whether the comment deletion request succeeds without a CSRF token or with only an HMAC token present
    Affected if Deletion requests succeed via GET method without proper CSRF token validation or referer checking

You are affected if wpDiscuz version is below 7.6.47 and the comment deletion functionality is accessible via GET requests using an HMAC key without CSRF protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.6.47 or later
Fixed in 7.6.47
Interim mitigation

Upgrade wpDiscuz to version 7.6.47 or later, which includes proper CSRF protection. Until then, consider disabling comment deletion functionality or implementing additional request validation at the WAF level.

Recommended fix High confidence

wpDiscuz version 7.6.47

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the wpDiscuz plugin
  4. Click Update Now or check for updates to get version 7.6.47 or later
  5. After updating, verify the plugin version shows 7.6.47 or newer in the plugins list
  6. Review comment activity logs to ensure no unauthorized comment deletions occurred

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22202 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data