advancedcoding Comments Plugin up to 7.6.56 on WordPress HTML Attribute getCommentAuthor HTML injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 1.53+ |
Summary
A vulnerability was found in advancedcoding Comments Plugin up to 7.6.56 on WordPress. It has been rated as problematic. Affected is the function getCommentAuthor of the component HTML Attribute Handler. Performing a manipulation results in HTML injection.
This vulnerability is cataloged as CVE-2026-9148. It is possible to initiate the attack remotely. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability was found in advancedcoding Comments Plugin up to 7.6.56 on WordPress. It has been classified as problematic. This affects the function getCommentAuthor of the component HTML Attribute Handler. The manipulation with an unknown input leads to a html injection vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:
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.
The weakness was shared by mickeyjoe. The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2026-9148 since 05/20/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 7.6.48 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 7.6.0
- 7.6.1
- 7.6.2
- 7.6.3
- 7.6.4
- 7.6.5
- 7.6.6
- 7.6.7
- 7.6.8
- 7.6.9
- 7.6.10
- 7.6.11
- 7.6.12
- 7.6.13
- 7.6.14
- 7.6.15
- 7.6.16
- 7.6.17
- 7.6.18
- 7.6.19
- 7.6.20
- 7.6.21
- 7.6.22
- 7.6.23
- 7.6.24
- 7.6.25
- 7.6.26
- 7.6.27
- 7.6.28
- 7.6.29
- 7.6.30
- 7.6.31
- 7.6.32
- 7.6.33
- 7.6.34
- 7.6.35
- 7.6.36
- 7.6.37
- 7.6.38
- 7.6.39
- 7.6.40
- 7.6.41
- 7.6.42
- 7.6.43
- 7.6.44
- 7.6.45
- 7.6.46
- 7.6.47
- 7.6.48
- 7.6.49
- 7.6.50
- 7.6.51
- 7.6.52
- 7.6.53
- 7.6.54
- 7.6.55
- 7.6.56
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.2
CNA Vector (Wordfence): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: HTML injectionCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Comments Plugin 7.6.48
Timeline
05/20/2026 CVE reserved07/03/2026 Advisory disclosed
07/03/2026 VulDB entry created
07/03/2026 VulDB entry last update
Sources
Advisory: wordfence.comResearcher: mickeyjoe
Status: Confirmed
CVE: CVE-2026-9148 (🔒)
GCVE (CVE): GCVE-0-2026-9148
GCVE (VulDB): GCVE-100-376089
Entry
Created: 07/03/2026 15:33Changes: 07/03/2026 15:33 (68)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.