WordPress Core < 6.0.2 - Authenticated SQL Injection

2022-08-30 00:00
FVD

Strategic Overview

Status
Patched in 3.7.39
Affected Core
WordPress 6.0
Affected Version
3.6.1 – 6.0.1 · 25 branches
CVSS
8.0High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE pending
View all WordPress 6.0 vulnerabilities

At a glance

This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WordPress 6.0 WordPress release line, affecting 3.6.1 – 6.0.1 · 25 branches. It carries a CVSS score of 8.0 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 3.7.39; sites on affected versions should update now. Disclosed August 2022, reported by FVD.

Vulnerability Overview

WordPress Core, in versions up to 6.0.2, is vulnerable to SQL Injection that can be exploited by authenticated users via the LIMIT parameter passed through the get_bookmarks function. This can be exploited on default WordPress installations by users with high-level privileges, such as an editor or administrator, and it may be possible for this to be exploited by lower-privileged users if a plugin/theme passes an unescaped user supplied LIMIT value from those level users to the get_bookmarks function.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in WordPress 6.0 3.6.1 – 6.0.1 · 25 branches takes any authenticated account. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WordPress 6.0 the fix is 3.7.39: builds 3.6.1 – 6.0.1 · 25 branches are affected, anything from 3.7.39 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 3.7.39, 3.8.39, 3.9.37, 4.0.36, 4.1.36, 4.2.33, 4.3.29, 4.4.28, 4.5.27, 4.6.24, 4.7.24, 4.8.20, 4.9.21, 5.0.17, 5.1.14, 5.2.16, 5.3.13, 5.4.11, 5.5.10, 5.6.9, 5.7.7, 5.8.5, 5.9.4, 6.0.2

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress 6.0: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 3.7.39 is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/0248f829-84de-40b9-bb63-354fbf06472d

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C