Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2022-21663

WordPress is a free and open-source content management system written ...

Overview

Published
6 Jan 2022
Modified
17 Jun 2026
High CVE
2 Registry packages
1 OS packages
2 Linux distributions
Yes Fix available

Description

WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. On a multisite, users with Super Admin role can bypass explicit/additional hardening under certain conditions through object injection. 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 issue.

Source: OX vulnerability database

Severity

7.2 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-74, CWE-502

Affected packages · 2

Packages affected by CVE-2022-21663
EcosystemPackageVulnerableFixed in
Bitnami wordpress <5.8.3 5.8.3
Bitnami wordpress-multisite <5.8.3 5.8.3

Open a package to see all its vulnerabilities.

Operating systems · 7 fixes

debian 6 releases · 1 package

fixed 6
wordpress
debian fixes for CVE-2022-21663
ReleasePackageFixed in
10 wordpress 5.0.15+dfsg1-0+deb10u1
11 wordpress 5.7.5+dfsg1-0+deb11u1
12 wordpress 5.8.3+dfsg1-1
13 wordpress 5.8.3+dfsg1-1
14 wordpress 5.8.3+dfsg1-1
9 wordpress 4.7.22+dfsg-0+deb9u1

echo 1 release · 1 package

fixed 1
wordpress
echo fixes for CVE-2022-21663
ReleasePackageFixed in
wordpress 5.8.3+dfsg1-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.