{"id":"BIT-wp-cli-2021-29504","summary":"Improper Certificate Validation in WP-CLI framework","details":"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.","aliases":["CVE-2021-29504","GHSA-rwgm-f83r-v3qj"],"modified":"2026-09-10T16:01:48.484421397Z","published":"2024-03-06T11:08:47.759Z","database_specific":{"severity":"Critical","cpes":["cpe:2.3:a:wp-cli:wp-cli:*:*:*:*:*:*:*:*"]},"references":[{"type":"ADVISORY","url":"https://github.com/wp-cli/checksum-command/pull/86"},{"type":"ADVISORY","url":"https://github.com/wp-cli/config-command/pull/128"},{"type":"ADVISORY","url":"https://github.com/wp-cli/core-command/pull/186"},{"type":"ADVISORY","url":"https://github.com/wp-cli/extension-command/pull/287"},{"type":"ADVISORY","url":"https://github.com/wp-cli/package-command/pull/138"},{"type":"ADVISORY","url":"https://github.com/wp-cli/wp-cli/pull/5523"},{"type":"ADVISORY","url":"https://github.com/wp-cli/wp-cli/security/advisories/GHSA-rwgm-f83r-v3qj"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-29504"}],"affected":[{"package":{"name":"wp-cli","ecosystem":"Bitnami","purl":"pkg:bitnami/wp-cli"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0.12.0"},{"fixed":"2.5.0"}]}],"database_specific":{"source":"https://github.com/bitnami/vulndb/tree/main/data/wp-cli/BIT-wp-cli-2021-29504.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"}]}],"schema_version":"1.9.0"}