CVE-2026-9148 json
Comments <= 7.6.56 - Unauthenticated Stored Cross-Site Scripting via 'Website' Field
published 4mo ago modified 4mo ago also EUVD-2026-41514
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-9148 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- advancedcoding Comments – wpDiscuz
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/f509f1c6-6094-434d-8e70-ad8419250aa2?source=cve
- plugins.trac.wordpress.org /browser/wpdiscuz/tags/7.6.54/utils/class.WpdiscuzHelper.php#L1619
- plugins.trac.wordpress.org /browser/wpdiscuz/tags/7.6.54/utils/class.WpdiscuzHelper.php#L1615
- plugins.trac.wordpress.org /browser/wpdiscuz/tags/7.6.54/forms/wpdFormAttr/Field/DefaultField/Website.php#L119
- plugins.trac.wordpress.org /browser/wpdiscuz/tags/7.6.54/forms/wpdFormAttr/Tools/Sanitizer.php#L14
- plugins.trac.wordpress.org /browser/wpdiscuz/tags/7.6.48/utils/class.WpdiscuzHelper.php#L1619
- plugins.trac.wordpress.org /browser/wpdiscuz/tags/7.6.48/utils/class.WpdiscuzHelper.php#L1615
- plugins.trac.wordpress.org /browser/wpdiscuz/tags/7.6.48/forms/wpdFormAttr/Field/DefaultField/Website.php#L119
- plugins.trac.wordpress.org /browser/wpdiscuz/tags/7.6.48/forms/wpdFormAttr/Tools/Sanitizer.php#L14
- plugins.trac.wordpress.org /changeset/3563675/wpdiscuz/trunk/utils/class.WpdiscuzHelper.php
- plugins.trac.wordpress.org /changeset?old_path=%2Fwpdiscuz/tags/7.6.56&new_path=%2Fwpdiscuz/tags/7.6.57
Sources
- CVE List CVE-2026-9148
- NVD CVE-2026-9148
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.