CVE-2025-14468

AMP for WP – Accelerated Mobile Pages <= 1.1.9 - Cross-Site Request Forgery to Comment Submission

2026-01-06 16:00
0N0ise

Strategic Overview

Status
Patched in 1.1.10
Affected Plugin
AMP for WP – Accelerated Mobile Pages
Affected Version
<= 1.1.9
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-14468
View all AMP for WP – Accelerated Mobile Pages vulnerabilities

At a glance

CVE-2025-14468 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the AMP for WP WordPress plugin, affecting versions <= 1.1.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.10; sites on affected versions should update now. Disclosed January 2026, reported by 0N0ise.

Vulnerability Overview

The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.9. This is due to inverted nonce verification logic in the amp_theme_ajaxcomments AJAX handler, which rejects requests with VALID nonces and accepts requests with MISSING or INVALID nonces. This makes it possible for unauthenticated attackers to submit comments on behalf of logged-in users via a forged request granted they can trick a user into performing an action such as clicking on a link, and the plugin's template mode is enabled.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in AMP for WP <= 1.1.9 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For AMP for WP the fix is 1.1.10: builds <= 1.1.9 are affected, anything from 1.1.10 onward is not.

Remediation

Update to version 1.1.10, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to AMP for WP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: AMP for WP 1.1.10 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14468https://www.wordfence.com/threat-intel/vulnerabilities/id/0d195034-4617-474d-a4b1-b299c1607f89https://nvd.nist.gov/vuln/detail/CVE-2025-14468

Related records

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