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.
CVE-2026-9148
HIGHPre-NVD 7.27.2—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. a secondary CVSS source baseline 7.2; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.2Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(high)
- EPSS
- 22.3%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 6, 2026
References (11)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpdiscuz/tags/7.6.48/forms/wpdFormAttr/Field/DefaultField/Website.php#L119
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpdiscuz/tags/7.6.48/forms/wpdFormAttr/Tools/Sanitizer.php#L14
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpdiscuz/tags/7.6.48/utils/class.WpdiscuzHelper.php#L1615
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpdiscuz/tags/7.6.48/utils/class.WpdiscuzHelper.php#L1619
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpdiscuz/tags/7.6.54/forms/wpdFormAttr/Field/DefaultField/Website.php#L119
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpdiscuz/tags/7.6.54/forms/wpdFormAttr/Tools/Sanitizer.php#L14
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpdiscuz/tags/7.6.54/utils/class.WpdiscuzHelper.php#L1615
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wpdiscuz/tags/7.6.54/utils/class.WpdiscuzHelper.php#L1619
- security@wordfencehttps://plugins.trac.wordpress.org/changeset/3563675/wpdiscuz/trunk/utils/class.WpdiscuzHelper.php
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?old_path=%2Fwpdiscuz/tags/7.6.56&new_path=%2Fwpdiscuz/tags/7.6.57
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/f509f1c6-6094-434d-8e70-ad8419250aa2?source=cve
Vendor Advisories for CVE-2026-9148(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 00:41 UTCEG score recompute
- 2026-07-07 00:41 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 12:05 UTCEG score recompute
- 2026-07-06 12:05 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:27 UTCEG score recompute
- 2026-07-05 23:27 UTCGHSA enrichment
- 2026-07-05 10:51 UTCEG score recompute
- 2026-07-05 10:51 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-04 22:15 UTCEG score recompute
- 2026-07-04 22:15 UTCGHSA enrichment
- 2026-07-04 09:39 UTCEG score recompute
- 2026-07-04 09:39 UTCGHSA enrichment
- 2026-07-03 21:04 UTCEG score recompute
- 2026-07-03 21:03 UTCGHSA enrichment
- 2026-07-03 08:27 UTCEG score recompute
- 2026-07-03 08:26 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-9148?
CVE-2026-9148 is a high vulnerability published on July 3, 2026. 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 commentauthorurl…
When was CVE-2026-9148 disclosed?
CVE-2026-9148 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9148 actively exploited?
CVE-2026-9148 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9148?
CVE-2026-9148 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-9148?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9148, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-9148
Is Your Infrastructure Affected by CVE-2026-9148?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.