There are 5 open security issues in bookworm.
1 important issue:
- CVE-2019-8943:
WordPress through 5.0.3 allows Path Traversal in wp_crop_image(). An attacker (who has privileges to crop an image) can write the output image to an arbitrary directory via a filename containing two image extensions and ../ sequences, such as a filename ending with the .jpg?/../../file.jpg substring.
2 issues left for the package maintainer to handle:
- CVE-2022-3590:
(postponed; to be fixed through a stable update)
WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden.
- TEMP-1036689-1CA7FB:
(postponed; to be fixed through a stable update)
You can find information about how to handle these issues in the security team's documentation.
2 ignored issues:
- CVE-2012-6707:
WordPress through 4.8.2 uses a weak MD5-based password hashing algorithm, which makes it easier for attackers to determine cleartext values by leveraging access to the hash values. NOTE: the approach to changing this may not be fully compatible with certain use cases, such as migration of a WordPress site from a web host that uses a recent PHP version to a different web host that uses PHP 5.2. These use cases are plausible (but very unlikely) based on statistics showing widespread deployment of WordPress with obsolete PHP versions.
- CVE-2023-5692:
WordPress Core is vulnerable to Sensitive Information Exposure in versions up to, and including, 6.4.3 via the redirect_guess_404_permalink function. This can allow unauthenticated attackers to expose the slug of a custom post whose 'publicly_queryable' post status has been set to 'false'.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/w/wordpress.png){kind=link}