CVE-2026-2027 MEDIUM

CVE-2026-2027: AMP Enhancer <= 1.0.49 - Authenticated (Administrator+) Stored Cross-Site Scripting via AMP Custom CSS Setting

Vendor Ampenhancer
Product AMP Enhancer – Compatibility Layer for Official AMP Plugin
Weakness CWE-79 · XSS
Published February 14, 2026
Last update April 8, 2026

CVSS base score

4.4/10
Attack vector Network
Attack complexity High
Privileges required High
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

The AMP Enhancer – Compatibility Layer for Official AMP Plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the AMP Custom CSS setting in all versions up to, and including, 1.0.49 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Explanation of Vulnerability in Simple Terms

02Summary

AMP Enhancer versions up to 1.0.49 contain a cross-site scripting (XSS) vulnerability that allows high-privilege users to inject malicious scripts. The vulnerability requires high attack complexity and affects the integrity and confidentiality of data across the site scope. An administrator or high-privilege account is needed to exploit this issue.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that execute in other users' browsers and compromise site data.

Potential impact on your site

04Site Impact

A compromised admin account could inject scripts affecting all site visitors and leak sensitive data.

Conditions required to exploit

05Prerequisites

High-privilege account (administrator or equivalent) with network access; no user interaction required.

Key dates

06Disclosure timeline

February 14, 2026 CVE published
April 8, 2026 Record updated