CVE-2026-6101

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

Strategic Overview

Status
Patched in 1.1.13
Affected Version
<= 1.1.12
CVSS
7.5High
Weakness type
CWE-73 · External Control of File Name or Path
CVE
CVE-2026-6101
View all AMP for WP – Accelerated Mobile Pages vulnerabilities

At a glance

CVE-2026-6101 is a high-severity External Control of File Name or Path vulnerability in the AMP for WP WordPress plugin, affecting versions <= 1.1.12. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 1.1.13; sites on affected versions should update now. Disclosed July 2026, reported by Leonid Semenenko (lsemenenko).

Vulnerability Overview

The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Arbitrary File Write in versions up to and including 1.1.12. This is due to unsafe ZIP file extraction in the ampforwp_save_local_font() function combined with inadequate cleanup that fails to remove nested directories and files. This makes it possible for authenticated attackers, with Author-level access and above, and permissions granted by an Administrator, to write arbitrary files to the server in a web-accessible location, potentially leading to remote code execution on hosts that execute PHP files in the uploads directory.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-73: External Control of File Name or Path

The product allows user input to control or influence paths or file names that are used in filesystem operations.

Remediation

Update to version 1.1.13, or a newer patched version

How does WordSec protect against this?

An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: AMP for WP 1.1.13 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C