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.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 02 Sep 2026 08:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-89 |
Wed, 02 Sep 2026 06:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Comments – wpDiscuz < 7.6.66 - Unauthenticated Comment Disclosure via SQLi | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-09-02T10:45:58.294Z
Reserved: 2026-08-13T08:41:49.870Z
Link: CVE-2026-19704
No data.
Status : Received
Published: 2026-09-02T06:17:16.937
Modified: 2026-09-02T06:17:16.937
Link: CVE-2026-19704
No data.
OpenCVE Enrichment
Updated: 2026-09-02T08:00:14Z
-
CWE-89
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')