CVE-2021-29504Improper Certificate Validation in WP-CLI framework
- 9.1CriticalCVSS base score
- 1.3%Exploitation in 30 daysEPSS · top 29% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
WP-CLI is the command-line interface for WordPress. An improper error handling in HTTPS requests management in WP-CLI version 0.12.0 and later allows remote attackers able to intercept the communication to remotely disable the certificate verification on WP-CLI side, gaining full control over the communication content, including the ability to impersonate update servers and push malicious updates towards WordPress instances controlled by the vulnerable WP-CLI agent, or push malicious updates toward WP-CLI itself. The vulnerability stems from the fact that the default behavior of `WP_CLI\Utils\http_request()` when encountering a TLS handshake error is to disable certificate validation and retry the same request. The default behavior has been changed with version 2.5.0 of WP-CLI and the `wp-cli/wp-cli` framework (via https://github.com/wp-cli/wp-cli/pull/5523) so that the `WP_CLI\Utils\http_request()` method accepts an `$insecure` option that is `false` by default and consequently that a TLS handshake failure is a hard error by default. This new default is a breaking change and ripples through to all consumers of `WP_CLI\Utils\http_request()`, including those in separate WP-CLI bundled or third-party packages. https://github.com/wp-cli/wp-cli/pull/5523 has also added an `--insecure` flag to the `cli update` command to counter this breaking change. There is no direct workaround for the default insecure behavior of `wp-cli/wp-cli` versions before 2.5.0. The workaround for dealing with the breaking change in the commands directly affected by the new secure default behavior is to add the `--insecure` flag to manually opt-in to the previous insecure behavior.
Timeline
ID reserved
By GitHub_M
- 2 months later
· 2 months later
Published
- 3 years later
· 3 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVDNVD · Modified | 3.1 | High7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
- EPSS (exploitation in 30 days)
- 1.3% · top 29% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.1.
Affected products
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- Packagistwp-cli/wp-cliGHSA-rwgm-f83r-v3qj (opens in a new tab)
References
References7
- https://github.com/wp-cli/wp-cli/security/advisories/GHSA-rwgm-f83r-v3qj (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://github.com/wp-cli/checksum-command/pull/86 (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/wp-cli/config-command/pull/128 (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/wp-cli/core-command/pull/186 (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/wp-cli/extension-command/pull/287 (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/wp-cli/package-command/pull/138 (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/wp-cli/wp-cli/pull/5523 (opens in a new tab)x_refsource_MISCx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2021-1189 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-rwgm-f83r-v3qj (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2021-29504)Record last updated .