CVE-2026-6101
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe AMP for WP plugin versions up to 1.1.12 contain an arbitrary file write vulnerability in the ampforwp_save_local_font() function due to unsafe ZIP file extraction without proper path sanitization, combined with incomplete cleanup that fails to remove nested directories. Authenticated attackers with Author-level access can write arbitrary files to web-accessible locations, potentially achieving RCE on servers that execute PHP in uploads directories.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify AMP for WP plugin is installedNavigate to WordPress admin > Plugins and locate 'AMP for WP' in the plugin list, or check the plugin file header in /wp-content/plugins/accelerated-mobile-pages/accelerated-moblie-pages.php for the Version commentAffected if The plugin is installed and the version is 1.1.12 or lower
-
Confirm installed version numberRead the Version field from the plugin header or query the database: SELECT option_value FROM wp_options WHERE option_name = 'ampforwp_plugin_version'Affected if Version is 1.1.12 or any version up to and including 1.1.12
-
Check if local font feature is in useInspect the WordPress media library for uploaded font files (woff, woff2, ttf, otf) in /wp-content/uploads/ampforwp/ directory, or check plugin settings under AMP > Design > Custom FontsAffected if Custom/local fonts have been uploaded and the local font feature is enabled in plugin settings
-
Examine uploads directory for anomalous filesList all files in /wp-content/uploads/ and subdirectories, looking for unexpected .php files, double-extensions, or nested directories that may not have been cleaned up after font uploads: find /wp-content/uploads/ -type f -name '*.php' -o -type d | head -50Affected if Unexpected PHP files exist in uploads directories or orphaned nested directories remain from incomplete cleanup operations
A user is affected if the AMP for WP plugin versions 1.1.12 or lower is installed, the local font feature is enabled, and arbitrary files can be written to web-accessible locations or anomalous files appear in upload directories.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of the plugin that implements proper path traversal validation during ZIP extraction and ensures complete cleanup of extracted files and directories. Until then, disable the local font feature and restrict the 'manage_options' capability to prevent abuse.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6101 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data