WordPress plugin · Updated daily · Source: Wordfence Intelligence

AMP for WP vulnerabilities: affected versions and fixes

AMP for WP has 70,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

AMP for WP at a glance

  • 19 publicly disclosed vulnerabilities, 5 of them rated High or Critical. The most recent was disclosed on Nov 17, 2026.
  • Ranked #568 by popularity on WordPress.org (70,000+ active installs).
  • The latest version is 1.1.20 (released Nov 6, 2026). The most recent security fix shipped in 1.1.20.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your AMP for WP version

Enter the AMP for WP version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “AMP for WP”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “AMP for WP”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (1.1.20). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known AMP for WP vulnerabilities

  • AMP for WP <= 1.1.19 - Unauthenticated Stored Cross-Site Scripting via Comment Content

    Cross-site scripting (XSS) · CVE-2026-120686

    Affected versions: ≤ 1.1.19

    Fixed in: 1.1.20

    Severity: High 7.2 · Disclosed Nov 17, 2026

  • AMP for WP <= 1.1.18 - Authenticated (Subscriber+) Arbitrary Shortcode Execution via Author Biographical Info

    Other weakness · CVE-2026-103908

    Affected versions: ≤ 1.1.18

    Fixed in: 1.1.19

    Severity: Medium 5.4 · Disclosed Nov 5, 2026

  • AMP for WP <= 1.1.17 - Unauthenticated Stored Cross-Site Scripting via 'headline-*' Shortcode Attribute

    Cross-site scripting (XSS) · CVE-2026-97019

    Affected versions: ≤ 1.1.17

    Fixed in: 1.1.18

    Severity: High 7.2 · Disclosed Oct 27, 2026

  • AMP for WP <= 1.1.16 - Unauthenticated Stored Cross-Site Scripting via Comment Content Regex Transformation

    Cross-site scripting (XSS) · CVE-2026-83591

    Affected versions: ≤ 1.1.16

    Fixed in: 1.1.17

    Severity: High 7.2 · Disclosed Sep 24, 2026

  • AMP for WP <= 1.1.12 - Authenticated (Author+) Arbitrary File Write via Role-Based Access Configuration with Local Font Upload

    Other weakness · CVE-2026-6101

    Affected versions: ≤ 1.1.12

    Fixed in: 1.1.13

    Severity: High 7.5 · Disclosed Jul 6, 2026

  • AMP for WP <= 1.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting via SVG File Upload

    Cross-site scripting (XSS) · CVE-2026-0627

    Affected versions: ≤ 1.1.10

    Fixed in: 1.1.11

    Severity: Medium 6.4 · Disclosed Jan 8, 2026

  • AMP for WP – Accelerated Mobile Pages <= 1.1.9 - Cross-Site Request Forgery to Comment Submission

    Cross-site request forgery (CSRF) · CVE-2025-14468

    Affected versions: ≤ 1.1.9

    Fixed in: 1.1.10

    Severity: Medium 4.3 · Disclosed Jan 6, 2026

  • AMP for WP – Accelerated Mobile Pages <= 1.1.1 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-11254

    Affected versions: ≤ 1.1.1

    Fixed in: 1.1.2

    Severity: Medium 6.1 · Disclosed Dec 17, 2024

  • AMP for WP – Accelerated Mobile Pages <= 1.0.99.1 - Cross-Site Request Forgery to Privilege Escalation

    Cross-site request forgery (CSRF) · CVE-2024-9598

    Affected versions: ≤ 1.0.99.1

    Fixed in: 1.0.99.2

    Severity: High 8.8 · Disclosed Oct 24, 2024

  • AMP for WP <= 1.0.96.1 - Missing Authorization

    Missing authorization · CVE-2024-43146

    Affected versions: ≤ 1.0.96.1

    Fixed in: 1.0.97

    Severity: Medium 4.3 · Disclosed Aug 7, 2024

  • AMP for WP – Accelerated Mobile Pages <= 1.0.96.1 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload

    Cross-site scripting (XSS) · CVE-2024-6896

    Affected versions: ≤ 1.0.96.1

    Fixed in: 1.0.97

    Severity: Medium 6.4 · Disclosed Jul 23, 2024

  • AMP for WP <= 1.0.93.1 - Authenticated(Contributor+) Arbitrary Post Deletion via amppb_remove_saved_layout_data

    Missing authorization · CVE-2024-1043

    Affected versions: ≤ 1.0.93.1

    Fixed in: 1.0.93.2

    Severity: Medium 6.5 · Disclosed Feb 6, 2024

  • Accelerated Mobile Pages <= 1.0.92.1 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-0587

    Affected versions: ≤ 1.0.92.1

    Fixed in: 1.0.93

    Severity: Medium 6.1 · Disclosed Jan 22, 2024

  • AMP for WP – Accelerated Mobile Pages <= 1.0.92 - Authenticated (Contributor+) Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2023-6782

    Affected versions: ≤ 1.0.92

    Fixed in: 1.0.92.1

    Severity: Medium 6.4 · Disclosed Dec 18, 2023

  • Accelerated Mobile Pages <= 1.0.88.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via shortcode

    Cross-site scripting (XSS) · CVE-2023-48321

    Affected versions: ≤ 1.0.88.1

    Fixed in: 1.0.89

    Severity: Medium 6.4 · Disclosed Nov 28, 2023

  • AMP for WP <= 1.0.77.32 - Authenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-23209

    Affected versions: ≤ 1.0.77.32

    Fixed in: 1.0.77.33

    Severity: Medium 5.5 · Disclosed Dec 15, 2021

  • AMP for WP – Accelerated Mobile Pages <= 1.0.77.31 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-23150

    Affected versions: ≤ 1.0.77.31

    Fixed in: 1.0.77.32

    Severity: Medium 5.5 · Disclosed Dec 11, 2021

  • AMP for WP <= 0.9.97.20 - Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2018-20838

    Affected versions: ≤ 0.9.97.20

    Fixed in: 0.9.97.21

    Severity: Medium 5.4 · Disclosed Nov 20, 2018

  • AMP for WP <= 0.9.97.19 - Missing Authorization

    Missing authorization

    Affected versions: ≤ 0.9.97.19

    Fixed in: 0.9.97.20

    Severity: Medium 6.3 · Disclosed Oct 20, 2018

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 17, 2026.

Most common weaknesses in AMP for WP

Cross-site scripting (XSS)

12 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

3 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Cross-site request forgery (CSRF)

2 issues

If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.

Frequently asked questions

Is AMP for WP safe to use?

AMP for WP is a well-known plugin with 70,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (1.1.20) and turn on automatic updates.

How do I find which version of AMP for WP my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesAMP for WP on WordPress.org