WordPress: A security weakness

WordPress is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 6.6 CVSS 3.1 · security-advisories@github.com

NVD score 7.2 CVSS 3.1 · nvd@nist.gov

Component: WordPress
Plugin slug: Not applicable
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Jan 06, 2022
Weakness: CWE-74 — Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
CWE-502 — Deserialization of Untrusted Data

What to do

Update, patch or deactivate.

Update WordPress to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical 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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

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

References

Update, patch or deactivate.

Technical description

Primary and upstream sources