CVE-2026-120686: AMP for WP <= 1.1.19 - Unauthenticated Stored Cross-Site Scripting via Comment Content

Published Nov 18, 2026
·
Updated

The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.1.19 via comment content rendered on AMP post pages. The plugin registers an output-buffer callback ampforwpthecontentfilterfull() on the 'wp' action (priority 999) that applies a set of tag-agnostic and quote-agnostic regular expressions — notably /onclick=[^>]/ — to the entire AMP page output after approved comments have already been echoed into it; these regexes do not understand HTML tag or attribute-value boundaries, so a kses-legal comment that places strings like 'onclick="' inside a title attribute value can trigger deletion of the title's closing quote, causing the browser to re-parse what was previously textual content inside the attribute value as live HTML attributes. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, after an administrator has approved the comment.

Affected Software

1 affected component
Ampforwp AMP for WP – Accelerated Mobile Pages<=1.1.19

Event History

Nov 18, 2026
CVE Published
via MITRE·11:30 AM
Data Sourced
via MITRE·11:30 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue, and what conditions are required?

An unauthenticated attacker can submit a crafted comment. Exploitation requires an administrator to approve that comment, after which the payload executes when someone visits the affected AMP post page.

2

Are sites with comment moderation enabled still exposed?

Yes. Moderation does not prevent exploitation if an administrator approves the crafted comment; approval is explicitly part of the attack path.

3

Which visitors are at risk after a malicious comment is approved?

Any user who accesses the AMP version of the post containing the approved malicious comment may execute the injected script in their browser. The issue affects AMP post pages where comment content is rendered.

4

How can administrators check for possible exploitation?

Review approved comments associated with AMP posts for suspicious crafted content, especially strings such as onclick=" embedded within attribute values like title attributes. Because the payload relies on output rewriting, comments that appear otherwise permitted may still become executable on rendered AMP pages.

5

What can be done if an update cannot be applied immediately?

Prevent untrusted comments from being approved and review existing approved comments before they are displayed on AMP post pages. Removing suspicious approved comments eliminates the described injection source.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203