CVE-2026-120686

HIGH
Published November 18, 2026

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 ampforwp_the_content_filter_full() on the 'wp' action...

Full CISO analysis pending enrichment.

What systems are affected?

PackageEcosystemVulnerable RangePatched
Acceleratepip—No patch
9.9KOpenSSF 6.63.1K dependentsPushed 4d ago20% patched~6d to patchFull package profile →

Do you use Accelerate? You're affected.

How severe is it?

CVSS 3.1
7.2 / 10
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
N/A

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRNone
UINone
SChanged
CLow
ILow
ANone

What should I do?

No patch available

Monitor for updates. Consider compensating controls or temporary mitigations.

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-120686?

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 ampforwp_the_content_filter_full() 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.

Is CVE-2026-120686 actively exploited?

No confirmed active exploitation of CVE-2026-120686 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-120686?

No patch is currently available. Monitor vendor advisories for updates.

What is the CVSS score for CVE-2026-120686?

CVE-2026-120686 has a CVSS v3.1 base score of 7.2 (HIGH).

What are the technical details?

Original Advisory

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 ampforwp_the_content_filter_full() 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.

Weaknesses (CWE)

CWE-79 — Improper Neutralization of Input During Web Page Generation: The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

  • [Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
  • [Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Timeline

Published
November 18, 2026
Last Modified
November 18, 2026
First Seen
November 18, 2026

Related Vulnerabilities