Unauthenticated HTML injection via unfiltered comment content
Published Aug 2, 2024 · Updated Apr 8, 2026
HTML injection in wpDiscuz 7.6.21 and earlier allows remote attackers to place attacker-chosen markup in WordPress comments. The comment-processing path in class.WpdiscuzCore.php accepts comment content without filtering HTML tags when rich editing is disabled. Guest commenting and the simple editor must be available; injected hyperlinks persist in displayed comment content.
Summary
What happened
HTML injection in wpDiscuz 7.6.21 and earlier allows remote attackers to place attacker-chosen markup in WordPress comments. The comment-processing path in class.WpdiscuzCore.php accepts comment content without filtering HTML tags when rich editing is disabled. Guest commenting and the simple editor must be available; injected hyperlinks persist in displayed comment content.
The record
- CVE
- CVE-2024-6704
- Published
- Aug 2, 2024
- Updated
- Apr 8, 2026
- Vendor
- gVectors Team
- Product
- wpDiscuz
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 2, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=7.6.21
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo