dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2026-22216

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 a missing rate limiting vulnerability that allows unauthenticated attackers to subscribe arbitrary email addresses to post notifications by sending POST requests to the wpdAddSubscription handler in class.WpdiscuzHelperAjax.php. Attackers can exploit LIKE wildcard characters in the subscription query to match multiple email addresses and generate unwanted notification emails to victim accounts.

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 lacks rate limiting on the wpdAddSubscription AJAX endpoint in class.WpdiscuzHelperAjax.php, allowing unauthenticated attackers to subscribe arbitrary email addresses to post notifications. Attackers can exploit LIKE wildcard characters in the subscription query to match multiple email addresses and generate unwanted notification emails.

MitigationUpdate wpDiscuz to version 7.6.47 or later to obtain the rate limiting fix for the subscription endpoint.

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. Locate the wpDiscuz plugin installation
    Access your WordPress site's plugins directory or check via wp-admin > Plugins. Identify the wpDiscuz plugin file path, typically at /wp-content/plugins/wpdiscuz/
    Affected if wpDiscuz plugin is not found on the system
  2. Check installed wpDiscuz version
    Read the main plugin file (usually wpdiscuz.php) or check the plugin header in wp-admin > Plugins > wpDiscuz to find the version number
    Affected if The installed version is less than 7.6.47 (for example, 7.6.45 or 7.6.46)
  3. Verify the vulnerable AJAX file exists
    Check if the file class.WpdiscuzHelperAjax.php exists in the wpDiscuz plugin directory at /wp-content/plugins/wpdiscuz/ajax/class.WpdiscuzHelperAjax.php
    Affected if The file exists and the plugin version is below 7.6.47
  4. Inspect the subscription endpoint for rate limiting
    Open class.WpdiscuzHelperAjax.php and search for the wpdAddSubscription method. Look for rate limiting controls such as nonce checks, request frequency limits, or throttling mechanisms around this endpoint
    Affected if No rate limiting or throttling code is found in the wpdAddSubscription method and version is below 7.6.47

You are affected if wpDiscuz is installed with a version lower than 7.6.47 and the wpdAddSubscription AJAX endpoint lacks rate limiting controls.

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

Update wpDiscuz to version 7.6.47 or later to obtain the rate limiting fix for the subscription endpoint.

Recommended fix High confidence

wpDiscuz version 7.6.47

  1. Backup your WordPress site database and files before making any changes
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate wpDiscuz in the plugin list
  5. If an update is available, click 'Update Now' to upgrade to version 7.6.47 or later
  6. Alternatively, download wpDiscuz 7.6.47 from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the version number in Plugins > Installed Plugins to confirm 7.6.47 or higher is installed

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

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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