Is pwa-for-wp-\&-amp (WordPress plugin) vulnerable?

WordPress pwa-for-wp-\&-amp has 3 known advisories in the phpwarden feed. Feed 2026.10.29.4, updated 2026-10-29.

3advisories

0critical

0on CISA KEV

0no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2021-4354	The PWA for WP & AMP for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the pwaforwp_splashscreen_	high	8.8	`<1.7.33`	`1.7.33`
CVE-2021-4366	The PWA for WP & AMP plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the pwaforwp_update_fe	medium	6.3	`<1.7.33`	`1.7.33`
CVE-2024-7759	The PWA for WP WordPress plugin before 1.7.72 does not sanitise and escape some of its settings, which could allow high privilege users suc	medium	4.8	`<1.7.72`	`1.7.72`

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.