Comments Plugin up to 7.6.65 on WordPress sql injection

Summaryinfo

A vulnerability has been found in Comments Plugin up to 7.6.65 and classified as critical. The impacted element is an unknown function. The manipulation leads to sql injection. This vulnerability is traded as CVE-2026-19704. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Comments Plugin up to 7.6.65. This issue affects an unknown part. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at wpscan.com. The identification of this vulnerability is CVE-2026-19704 since 08/13/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 7.6.66 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• Comments Plugin

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
• 7.6.57
• 7.6.58
• 7.6.59
• 7.6.60
• 7.6.61
• 7.6.62
• 7.6.63
• 7.6.64
• 7.6.65

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion