WordPress plugin · wordpress-ping-optimizer
Is WordPress Ping Optimizer safe?
Closed. Replace it.
wordpress.org closed it on Jan 19, 2024 (security issue), so it gets no more security fixes, and 3 flaws are on record. If your site runs it, move to a maintained alternative.
- Flaws on record
- 3
- High or critical
- 0
- Exploited
- none
Every recorded flaw
- Apr 10, 2024WordPress Ping Optimizer: Does not have CSRF checks in some placesCVE-2023-6385 · affects up to 2.35.1.3.0 · reported by WPScanMedium 4.3
- Mar 27, 2023Cross-Site Request Forgery (CSRF) vulnerability in Pankaj Jha WordPress Ping Optimizer plugin <= 2.35.1.2.3 versions.CVE-2022-30705 · fixed in 2.35.1.3.0 · reported by PatchstackMedium 5.4
- Sep 19, 2022WordPress Ping Optimizer: Does not have CSRF check in placeCVE-2022-1591 · fixed in 2.35.1.3.0 · reported by WPScanMedium 4.3
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.