A vulnerability was found in WordPress up to 5.8.2 (Content Management System). It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. As an impact it is known to affect confidentiality, integrity, and availability. An attacker might be able inject and/or alter existing SQL statements which would influence the database exchange. The summary by CVE is:

WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Due to lack of proper sanitization in one of the classes, there's potential for unintended SQL queries to be executed. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 4.1.34. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this issue.

The weakness was disclosed 01/07/2022 as GHSA-jp3p-gw8h-6x86. The advisory is shared at github.com. This vulnerability is known as CVE-2022-21664 since 11/16/2021. The exploitation appears to be easy. The attack can be launched remotely. The requirement for exploitation is a single authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/09/2022).

Upgrading to version 5.8.3 eliminates this vulnerability. Applying the patch c09ccfbc547d75b392dbccc1ef0b4442ccd3c957 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Productinfoedit

Type

• Content Management System

Name

• WordPress

CPE 2.3infoedit

• 🔒
• 🔒
• 🔒

CPE 2.2infoedit

• 🔒
• 🔒
• 🔒

CVSSv3infoedit

CVSSv2infoedit

Exploitinginfoedit

Threat Intelligenceinfoedit

Countermeasuresinfoedit

Timelineinfoedit

Sourcesinfoedit

Entryinfoedit

Comments