# CVE-2026-19704: Comments – wpDiscuz < 7.6.66 - Unauthenticated Comment Disclosure via SQLi

> Unauthenticated attackers can inject SQL to read hidden comments, including those awaiting moderation or on private posts, in the wpDiscuz plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-mjfm-w43c-xv7h

## What is CVE-2026-19704?

CVE-2026-19704 is a medium-severity SQL injection vulnerability in Unknown Comments, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-19704?


## How do I fix CVE-2026-19704?

No fix has been published for CVE-2026-19704 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19704 being exploited?

There is no known exploitation of CVE-2026-19704 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19704 and fix it if it is affected.

What it is: CVE-2026-19704 is a medium-severity SQL injection vulnerability in Unknown Comments, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19704 in the wild and no public exploit code.

Affected product: Unknown Comments. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19704/ (Markdown: https://insights.sbomify.com/CVE-2026-19704/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19704
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19704
- OSV: https://osv.dev/vulnerability/CVE-2026-19704

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19704/
Summaries are generated and may contain mistakes; the official description above is the record.