https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2024-11254.htmlhttps://patchthecve.com/cve/CVE-2024-11254.htmlWed, 17 Jun 2026 06:57:24 +0000MEDIUM 6.1: The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the disqus_name parameter in all versions up to, and including, 1.1.1 due to insufficient input validation. This makes it possible for unauthenticated attackers to inject arbitrary web https://patchthecve.com/cve/CVE-2024-9598.htmlhttps://patchthecve.com/cve/CVE-2024-9598.htmlWed, 17 Jun 2026 08:24:53 +0000HIGH 8.8: The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.99.1. This is due to missing or incorrect nonce validation on the 'proxy' function. This makes it possible for unauthenticated attackers to send the lohttps://patchthecve.com/cve/CVE-2024-6896.htmlhttps://patchthecve.com/cve/CVE-2024-6896.htmlWed, 17 Jun 2026 08:18:55 +0000MEDIUM 6.4: The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 1.0.96.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-https://patchthecve.com/cve/CVE-2024-1043.htmlhttps://patchthecve.com/cve/CVE-2024-1043.htmlWed, 17 Jun 2026 07:03:18 +0000MEDIUM 6.5: The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'amppb_remove_saved_layout_data' function in all versions up to, and including, 1.0.93.1. This makes it possible for authenticated attackers, with contrihttps://patchthecve.com/cve/CVE-2024-0587.htmlhttps://patchthecve.com/cve/CVE-2024-0587.htmlWed, 17 Jun 2026 06:53:50 +0000MEDIUM 6.1: The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'disqus_name' parameter in all versions up to, and including, 1.0.92.1 due to insufficient input sanitization and output escaping on the executed JS file. This makes it possible for