dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2026-22204

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

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 an email header injection vulnerability that allows attackers to manipulate mail recipients by injecting malicious data into the comment_author_email cookie. Attackers can craft a malicious cookie value that, when processed through urldecode() and passed to wp_mail() functions, enables header injection to alter email recipients or inject additional headers.

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 · moderate confidence

wpDiscuz before 7.6.47 is vulnerable to email header injection via the comment_author_email cookie. The cookie value is processed through urldecode() and passed to wp_mail() without proper sanitization, allowing attackers to inject newline characters and manipulate email recipients or add arbitrary email headers.

MitigationUpgrade wpDiscuz to version 7.6.47 or later to remediate this vulnerability.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 the WordPress plugins directory or query the wp_options table for 'active_plugins' and look for 'wpdiscuz' or 'wpDiscuz' in the plugin list. Alternatively, check the file system at /wp-content/plugins/ for a wpdiscuz folder.
    Affected if wpDiscuz plugin is not found in the WordPress installation
  2. Determine installed wpDiscuz version
    Check the plugin header comment in wpdiscuz.php (typically at /wp-content/plugins/wpdiscuz/functions.php or /wp-content/plugins/wpdiscuz/wpdiscuz.php) for the 'Version' field, or query the WordPress options table for the version stored by the plugin.
    Affected if The version found is less than 7.6.47 (e.g., 7.6.0, 7.5.0, etc.)
  3. Confirm comment submission feature is active
    Check WordPress settings at Settings > Discussion to ensure 'Allow people to post comments on new articles' is enabled, or inspect the wpDiscuz settings for comment form visibility.
    Affected if Comments are enabled and the wpDiscuz comment form is active on the site

You are affected if wpDiscuz is installed with a version lower than 7.6.47 and comment functionality using the wpDiscuz comment form is enabled on your site.

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 to remediate this vulnerability.

Recommended fix High confidence

wpDiscuz version 7.6.47

  1. 1. Backup your WordPress site database and files before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard > Plugins page.
  3. 3. Find the wpDiscuz plugin in the installed plugins list.
  4. 4. Click 'Update now' on the wpDiscuz plugin if an update is available, or manually update to version 7.6.47 or later.
  5. 5. Verify the update was successful by checking the installed version number.
  6. 6. Test that comment submission and email notifications still function correctly.

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

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22204 — 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-22204 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