CVE-2021-4366 json
PWA for WP & AMP < = 1.7.32 - Missing Authorization
published 3y ago modified 4mo ago also EUVD-2021-34193
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
The PWA for WP & AMP plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the pwaforwp_update_features_options function in versions up to, and including, 1.7.32. This makes it possible for authenticated attackers to change the otherwise restricted settings within the plugin.
Patch / fix
- magazine3 pwa_for_wp_&_amp 1.7.33
Is CVE-2021-4366 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.nintechnet.com https://blog.nintechnet.com/wordpress-pwa-for-wp-and-amp-plugin-fixed-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- magazine3 PWA for WP – Progressive Web Apps Made Simple
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
blog.nintechnet.com
/wordpress-pwa-for-wp-and-amp-plugin-fixed-vulnerabilities/
exploit, third-party-advisory
-
wordfence.com
/threat-intel/vulnerabilities/id/a9892dd1-3939-41a9-a828-fa1bf7d96eb8?source=cve
third-party-advisory
-
wpscan.com
/vulnerability/b38a51d7-375e-4cca-88ba-ccab796ac134
third-party-advisory
Sources
- CVE List CVE-2021-4366
- NVD CVE-2021-4366
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.