# CVE-2026-6101: File upload in AMP for WP – Accelerated Mobile Pages

> Authenticated attackers with Author access can write arbitrary files via unsafe ZIP extraction, potentially leading to remote code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-gw54-4vv6-gpqx

## What is CVE-2026-6101?

CVE-2026-6101 is a high-severity vulnerability in mohammed_kaludi AMP for WP – Accelerated Mobile Pages, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-6101?


## How do I fix CVE-2026-6101?

No fix has been published for CVE-2026-6101 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6101 being exploited?

There is no known exploitation of CVE-2026-6101 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6101 and fix it if it is affected.

What it is: CVE-2026-6101 is a high-severity vulnerability in mohammed_kaludi AMP for WP – Accelerated Mobile Pages, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6101 in the wild and no public exploit code.

Affected product: mohammed_kaludi AMP for WP – Accelerated Mobile Pages. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6101/ (Markdown: https://insights.sbomify.com/CVE-2026-6101/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6101
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6101
- OSV: https://osv.dev/vulnerability/CVE-2026-6101

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6101/
Summaries are generated and may contain mistakes; the official description above is the record.