Bug 2039301 (CVE-2022-21661) - CVE-2022-21661 wordpress: SQL injection via WP_Query
Summary: CVE-2022-21661 wordpress: SQL injection via WP_Query
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2022-21661
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2039302 2039303
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-11 13:20 UTC by Guilherme de Almeida Suckevicz
Modified: 2022-01-11 15:31 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-01-11 15:31:16 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2022-01-11 13:20:18 UTC
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Due to improper sanitization in WP_Query, there can be cases where SQL injection is possible through plugins or themes that use it in a certain way. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this vulnerability.

References:
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-6676-cqfm-gw84
https://wordpress.org/news/2022/01/wordpress-5-8-3-security-release/
https://www.zerodayinitiative.com/advisories/ZDI-22-020/

Upstream patch:
https://github.com/WordPress/wordpress-develop/commit/17efac8c8ec64555eff5cf51a3eff81e06317214

Comment 1 Guilherme de Almeida Suckevicz 2022-01-11 13:20:34 UTC
Created wordpress tracking bugs for this issue:

Affects: epel-7 [bug 2039303]
Affects: fedora-all [bug 2039302]

Comment 2 Product Security DevOps Team 2022-01-11 15:31:14 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.