WordPress security by component
PWA for WP
Plugin description
PWA for WP is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published May 15, 2025; the highest CVE/CNA score is 8.8.
Plugin slug:
pwa-for-wp-ampLatest vulnerability
CVE-2024-7759: PWA for WP: Cross-site scripting
PWA for WP is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
| Safe version |
|
||
|---|---|---|---|
| May 15, 2025 |
CVE-2024-7759
PWA for WP: Cross-site scripting
PWA for WP is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE4.8
NVDPending
|
| Nov 01, 2024 |
CVE-2024-47318
PWA for WP & AMP: A security weakness
PWA for WP & AMP is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVD8.8
|
| Jun 07, 2023 |
CVE-2021-4366
PWA for WP & AMP: A security weakness
PWA for WP & AMP is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE6.3
NVD4.3
|
| Jun 07, 2023 |
CVE-2021-4354
Pwa For Wp & Amp: Dangerous file upload
Pwa For Wp & Amp is affected by dangerous file upload. Exploitation requires an authenticated WordPress account. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise.
|
See mitigation notes |
CVE8.8
NVD8.8
|