WordPress through 6.1.1 depends on unpredictable client visits to cause wp-cron.php execution and the resulting security updates, and the source code describes "the scenario where a site may not receive enough visits to execute scheduled tasks in a timely manner," but neither the installation guide nor the security guide mentions this default behavior, or alerts the user about security risks on installations with very few visits.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-22622US | medium5.3 | Exploit | ||
WordPress through 6.1.1 depends on unpredictable client visits to cause wp-cron.php execution and the resulting security updates, and the source code describes "the scenario where… | ||||
02
references
External citations — patches, advisories, analysis.
- https://developer.wordpress.org/plugins/cron/ADVISORY
- https://github.com/WordPress/WordPress/blob/dca7b5204b5fea54e6d1774689777b359a9222ab/wp-cron.php#L5-L8ADVISORY
- https://medium.com/%40thecpanelguy/the-nightmare-that-is-wpcron-php-ae31c1d3ae30WEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-22622WEB
- https://patchstack.com/articles/solving-unpredictable-wp-cron-problems-addressing-cve-2023-22622/ADVISORY
- https://wordpress.org/about/security/ADVISORY
- https://wordpress.org/support/article/how-to-install-wordpress/ADVISORY
- https://www.tenable.com/plugins/was/113449ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan