Is waiting (WordPress plugin) vulnerable?

WordPress waiting has 5 known advisories in the phpwarden feed. Feed 2026.10.29.4, updated 2026-10-29.

5advisories
0critical
0on CISA KEV
5no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2023-28659The Waiting: One-click Countdowns WordPress Plugin, version <= 0.6.2, is affected by an authenticated SQL injection vulnerability in the pbchigh8.8<=0.6.2–
CVE-2023-2757The Waiting: One-click countdowns plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on 'saveLang'high7.4<=0.6.2–
CVE-2023-3999The Waiting: One-click countdowns plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on its AJAX camedium6.3<=0.6.2–
CVE-2022-4954The Waiting: One-click countdowns plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Countdown name in versions up tomedium5.5<=0.6.2–
CVE-2023-4000The Waiting: One-click countdowns plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 0.6.2. medium6.3<=0.6.2–

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden wordpress /var/www/html

# or, without Composer
pipx install phpwarden   &&   phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.