dbcve.org
WpdiscuzWordPress extension · Gvectors

CVE-2026-22210

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

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 cross-site scripting vulnerability that allows attackers to inject malicious code through unescaped attachment URLs in HTML output by exploiting the WpdiscuzHelperUpload class. Attackers can craft malicious attachment records or filter hooks to inject arbitrary JavaScript into img and anchor tag attributes, executing code in the context of WordPress users viewing comments.

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 contains a stored XSS vulnerability where attachment URLs are not escaped before being rendered in HTML output via the WpdiscuzHelperUpload class. Attackers can inject arbitrary JavaScript into img and anchor tag attributes by crafting malicious attachment records or filter hooks, executing code when WordPress users view comments containing these attachments.

MitigationUpgrade wpDiscuz to version 7.6.47 or later to patch the vulnerability. Until the patch is applied, consider disabling file attachments in comments or deploying a WAF with XSS filtering rules.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm wpDiscuz plugin installation and version
    Check the installed version by viewing the plugin header in wp-content/plugins/wpdiscuz/readme.txt, or via WordPress admin under Plugins > Installed Plugins, or by querying the wp_options table for the 'wpdiscuz_version' option.
    Affected if The installed version is less than 7.6.47 (e.g., 7.6.46, 7.6.45, etc.)
  2. Verify file attachment feature is enabled
    Navigate to wpDiscuz Settings > Comments > File Uploads in WordPress admin, or query the wp_options table for options containing 'wc_attachment' (e.g., wc_attachment_enable).
    Affected if File attachments in comments are enabled (the vulnerability only applies when users can attach files to comments).
  3. Inspect comment attachment records for malicious URLs
    Query the wp_comments table or related meta table for commentmeta entries with attachment URLs. Look for patterns like javascript:, data:, or unexpected HTML/script tags within URL fields that could indicate stored XSS payloads.
    Affected if Any comment records contain unsanitized attachment URLs with injected script tags or javascript: protocols in img src or anchor href attributes.

You are affected if wpDiscuz version is below 7.6.47 AND the file attachment feature is enabled, allowing attackers to inject malicious scripts via attachment URLs in comments.

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 patch the vulnerability. Until the patch is applied, consider disabling file attachments in comments or deploying a WAF with XSS filtering rules.

Recommended fix High confidence

wpDiscuz 7.6.47

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate wpDiscuz in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 7.6.47 from wordpress.org
  5. Verify the plugin version shows 7.6.47 or higher after updating
  6. Test comment functionality with attachments to confirm the plugin works correctly
  7. Clear any caching plugins if present

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

Fix this in Wpdiscuz Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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