taocms up to 3.0.2 Comment Update sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in taocms up to 3.0.2. This impacts an unknown function. The manipulation of the argument Comment Update leads to sql injection. This vulnerability is uniquely identified as CVE-2022-23387. No exploit exists.

Detailsinfo

A vulnerability was found in taocms up to 3.0.2 and classified as critical. This issue affects an unknown functionality. The manipulation of the argument Comment Update 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 weakness was disclosed 03/01/2022 as 23. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-23387 since 01/18/2022. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• taocms

Version

• 3.0.0
• 3.0.1
• 3.0.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion