WpdiscuzWordPress extension · Gvectors
CVE-2026-22182
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 · uneditedwpDiscuz before 7.6.47 contains an unauthenticated denial of service vulnerability that allows anonymous users to trigger mass notification emails by exploiting the checkNotificationType() function. Attackers can repeatedly call the wpdiscuz-ajax.php endpoint with arbitrary postId and comment_id parameters to flood subscribers with notifications, as the handler lacks nonce verification, authentication checks, and rate limiting.
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 confidencewpDiscuz before 7.6.47 has an unauthenticated DoS vulnerability in the wpdiscuz-ajax.php endpoint. The checkNotificationType() function lacks nonce verification, authentication checks, and rate limiting, allowing anonymous attackers to repeatedly send requests with arbitrary postId and comment_id parameters to trigger mass notification emails to subscribers, causing email flood DoS.
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
< 7.6.47CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify wpDiscuz plugin is installedCheck your WordPress site's wp-content/plugins directory for the wpdiscuz folder, or look for wpDiscuz in the WordPress admin plugins listAffected if The wpDiscuz plugin is not found on the system
-
Determine installed wpDiscuz versionLocate the main plugin file (usually wpdiscuz.php) and check the 'Version' header in the plugin comments, or view the version in WordPress admin > Plugins > wpDiscuzAffected if The installed version is less than 7.6.47 (e.g., 7.6.46, 7.6.0, etc.)
-
Verify vulnerable endpoint existsCheck for the existence of wpdiscuz-ajax.php in the wpdiscuz directory, typically at /wp-content/plugins/wpdiscuz/classes/wpdiscuz-ajax.phpAffected if The file wpdiscuz-ajax.php exists in the plugin directory
-
Confirm vulnerable function is presentSearch the wpdiscuz-ajax.php file for the checkNotificationType() function and verify it lacks nonce verification, authentication checks, and rate limiting logicAffected if The checkNotificationType() function exists and contains no nonce verification, no wp_verify_nonce call, no is_user_logged_in check, and no rate limiting
-
Test endpoint accessibility (optional)Send a crafted POST request to /wp-admin/admin-ajax.php with action=wpdiscuzNotification&postId=1&comment_id=1 from an unauthenticated source to observe if the server processes the requestAffected if The endpoint accepts and processes unauthenticated requests without returning a nonce or authentication error
You are affected if wpDiscuz is installed with a version earlier than 7.6.47 and the checkNotificationType() function in wpdiscuz-ajax.php lacks security controls, allowing unauthenticated notification triggers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.6.47
Update wpDiscuz to version 7.6.47 or later which implements nonce verification, authentication checks, and rate limiting on the notification endpoint.
wpDiscuz 7.6.47
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate wpDiscuz in the plugin list
- Click 'Update now' if an update is available, or manually update to version 7.6.47
- Verify the plugin version is 7.6.47 or higher after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wpdiscuz
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22182 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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