dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2026-22193

HIGH · 7.5 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 7.6.47 or later.
See remediation →
84/100
Remediation priority · High
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 SQL injection vulnerability in the getAllSubscriptions() function where string parameters lack proper quote escaping in SQL queries. Attackers can inject malicious SQL code through email, activation_key, subscription_date, and imported_from parameters to manipulate database queries and extract sensitive information.

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 has an SQL injection vulnerability in the getAllSubscriptions() function where the email, activation_key, subscription_date, and imported_from parameters lack proper SQL quote escaping, allowing attackers to inject malicious SQL code through these string parameters.

MitigationUpdate wpDiscuz to version 7.6.47 or later to obtain the vendor patch that implements proper SQL quote escaping for the affected parameters.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Check wpDiscuz plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins > wpDiscuz, or inspect the main plugin file (wpdiscuz.php) for the 'Version' header comment, or query via WP-CLI: wp plugin list --name=wpdiscuz --format=table
    Affected if The installed version is below 7.6.47 (e.g., 7.6.46, 7.5.x, 7.0.x, etc.)
  2. Identify subscription module usage
    Check if the wpDiscuz subscription/comment notification feature is enabled in wpDiscuz Settings > Subscription / Email Settings, or inspect database table prefixes for wpdiscuz_subscriptions entries
    Affected if The subscription feature is active and the getAllSubscriptions() function processes user-supplied subscription data
  3. Locate vulnerable function code
    Access the WordPress site files via FTP or file manager, navigate to /wp-content/plugins/wpdiscuz/ and locate the file containing getAllSubscriptions() (typically in class.WpdiscuzCore.php or similar), then inspect the function for unescaped parameters: email, activation_key, subscription_date, imported_from
    Affected if The function exists and these string parameters are processed without using $wpdb->prepare() or proper quote escaping (esc_sql())
  4. Review application logs for suspicious subscription queries
    Check WordPress debug log (wp-content/debug.log) or database slow query log for SQL injection patterns in subscription-related requests, or inspect web server access logs for unusual subscription POST/GET requests containing SQL metacharacters
    Affected if Logs show subscription-related SQL queries containing injected SQL syntax or unusual WHERE clause patterns

Your environment is affected if wpDiscuz version is below 7.6.47 AND the subscription feature is enabled, since the vulnerable getAllSubscriptions() function handles unsanitized string parameters for email, activation_key, subscription_date, and imported_from.

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 vendor patch that implements proper SQL quote escaping for the affected parameters.

Recommended fix High confidence

wpDiscuz 7.6.47

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Find wpDiscuz in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 7.6.47
  5. Verify the plugin updated successfully by checking the version number
  6. Test that comments and subscriptions functionality works correctly
Caveat Standard minor version update - review changelog for any configuration changes

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
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

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