dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2026-22183

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

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 stored cross-site scripting vulnerability in the inline comment preview functionality that allows authenticated users to inject malicious scripts by submitting comments with unescaped content. Attackers with unfiltered_html capabilities can inject JavaScript directly through comment content rendered in the AJAX response from the getLastInlineComments() function in class.WpdiscuzHelperAjax.php without proper HTML escaping.

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 a stored XSS vulnerability in the inline comment preview feature. The getLastInlineComments() function in class.WpdiscuzHelperAjax.php returns AJAX responses containing comment content without proper HTML escaping, allowing authenticated users with unfiltered_html capabilities to inject malicious JavaScript that executes when other users view the inline preview.

MitigationUpgrade wpDiscuz to version 7.6.47 or later which includes proper HTML escaping in the getLastInlineComments() function. Until then, restrict the unfiltered_html capability to trusted administrative users only.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 installation
    Check your WordPress plugins directory for wpdiscuz or look in wp-admin > Plugins for wpDiscuz
    Affected if wpDiscuz is installed and active
  2. Determine installed version
    Check the plugin version in the wpDiscuz plugin header (usually in the main plugin file or readme.txt) and compare to 7.6.47
    Affected if Version is less than 7.6.47
  3. Check if inline comment preview is enabled
    Navigate to wpDiscuz settings in WordPress admin and verify if the inline comment feature is turned on
    Affected if Inline comments are enabled and the version is below 7.6.47
  4. Audit user roles with unfiltered_html capability
    Review which user roles or specific users have the unfiltered_html capability (typically found in user editing or role management plugins)
    Affected if Non-admin users have unfiltered_html capability AND inline comments are enabled AND version is below 7.6.47

You are affected if wpDiscuz version is below 7.6.47, the inline comment preview feature is enabled, and users other than trusted administrators have the unfiltered_html capability.

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 HTML escaping in the getLastInlineComments() function. Until then, restrict the unfiltered_html capability to trusted administrative users only.

Recommended fix High confidence

7.6.47

  1. Update the wpDiscuz plugin to version 7.6.47 or later through the WordPress admin dashboard under Plugins > Installed Plugins
  2. Alternatively, navigate to Plugins > Add New > Upload and upload the updated wpDiscuz plugin zip file from wordpress.org

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

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-22183 — 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-22183 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