wpDiscuz permits unauthenticated comment-query injection
wpDiscuz before 7.6.66 uses an unvalidated visitor-controlled value as SQL query grammar. An unauthenticated attacker can read comments awaiting moderation, marked as spam or trash, or attached to private and draft posts. The disclosed injection exposes those comment records rather than arbitrary database contents.
- Component
- Comments
- Plugin slug
wpdiscuz- Affected
- < 7.6.66
- Safe version
7.6.66- Published
- Sep 02, 2026
This CVE was published Sep 02, 2026 and is one of 35 known issues for this plugin.
Update, patch or deactivate.
Update to wpDiscuz 7.6.66 or later and assess whether non-public comment content was exposed.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Comments WordPress plugin before 7.6.66 does not validate a value used to build a database query, allowing unauthenticated users to inject SQL and read comments they are not entitled to see, including comments awaiting moderation, comments marked as spam or trashed, and comments on private and draft posts. The injected text reaches the query as grammar rather than as data and does not yield extraction of arbitrary data, so the confidentiality impact is the disclosed comment content rather than the database at large.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N