Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9148

HIGH · 7.2 CVSS v3.1 Published 2026-07-03

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

81/100

Remediation priority · High

Remotely reachable No privileges Zero-click 7 weeks old

Official description

NVD · unedited

The Comments – wpDiscuz plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the guest commenter 'Website' field in versions up to, and including, 7.6.56 This is due to insufficient output escaping in the getCommentAuthor() function, which interpolates the stored comment_author_url value directly into single-quoted HTML attributes without applying esc_url() or esc_attr(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary

dbcve analysis · moderate confidence

The wpDiscuz WordPress plugin up to version 7.6.56 contains a stored XSS vulnerability in the getCommentAuthor() function where the guest commenter's website URL field is interpolated directly into single-quoted HTML attributes without esc_url() or esc_attr() escaping, allowing unauthenticated attackers to inject malicious scripts that execute when users view injected comments.

MitigationUpdate the wpDiscuz plugin to the latest version beyond 7.6.56, or implement proper output escaping (esc_url() or esc_attr()) on the comment_author_url value within the getCommentAuthor() function before HTML output.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify wpDiscuz plugin installation and version

Navigate to WordPress admin > Plugins > Installed Plugins and locate wpDiscuz; note the installed version number displayed

Affected if The installed version is 7.6.56 or lower
Confirm guest commenting is enabled

Check wpDiscuz settings at Settings > wpDiscuz > General Settings > Enable Guest Commenting is checked, or inspect WordPress admin settings for comment registration requirements

Affected if Guest comments are allowed, allowing unauthenticated attackers to submit comments with malicious URLs
Inspect getCommentAuthor function code

Locate the wpDiscuz plugin files (typically in wp-content/plugins/wpdiscuz/) and open the file containing getCommentAuthor() function; search for the code that handles comment_author_url output

Affected if The function directly outputs the website URL into HTML without esc_url() or esc_attr() wrapping (look for patterns like value='" . $comment_author_url . "' without escaping)
Examine rendered comment HTML output

Submit a test guest comment with a website URL containing a script tag (e.g., http://example.com/" onmouseover="alert(1)"), then view the comment in the frontend and inspect the HTML source

Affected if The URL appears unescaped in the HTML (script executes or the attribute contains raw URL data without proper encoding)

A user is affected if wpDiscuz version 7.6.56 or lower is installed, guest commenting is enabled, and the getCommentAuthor function outputs the comment author URL without esc_url() or esc_attr() escaping.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the wpDiscuz plugin to the latest version beyond 7.6.56, or implement proper output escaping (esc_url() or esc_attr()) on the comment_author_url value within the getCommentAuthor() function before HTML output.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing3.0 h
Review / QA1.0 h

7.0 hours of engineering $1,210

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9148 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-9148?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.2 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 7 hrs · Moderate

Typical engagement from $1,210

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-9148 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References