Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages

0
Medium
VulnerabilityCVE-2025-14468cvecve-2025-14468cwe-352
Published: Wed Jan 07 2026 (01/07/2026, 04:32:04 UTC)
Source: CVE Database V5
Vendor/Project: mohammed_kaludi
Product: AMP for WP – Accelerated Mobile Pages

Description

CVE-2025-14468 is a Cross-Site Request Forgery (CSRF) vulnerability in the AMP for WP – Accelerated Mobile Pages WordPress plugin, affecting all versions up to 1. 1. 9. The flaw arises from inverted nonce verification logic in the amp_theme_ajaxcomments AJAX handler, which mistakenly rejects valid nonces and accepts invalid or missing ones. This enables unauthenticated attackers to submit comments on behalf of logged-in users if they can trick them into clicking a malicious link, provided the plugin's template mode is enabled. The vulnerability has a medium severity with a CVSS score of 4. 3, reflecting limited impact on confidentiality and availability but potential integrity issues. No known exploits are currently reported in the wild. European organizations using this plugin in WordPress environments are at risk of unauthorized comment submissions, which could lead to reputational damage or content manipulation. Mitigation requires updating the plugin once a patch is available or disabling the vulnerable AJAX handler and template mode in the interim.

AI-Powered Analysis

AILast updated: 01/14/2026, 15:37:07 UTC

Technical Analysis

CVE-2025-14468 is a medium-severity CSRF vulnerability identified in the AMP for WP – Accelerated Mobile Pages plugin for WordPress, affecting all versions up to and including 1.1.9. The vulnerability stems from a logic error in the nonce verification process within the amp_theme_ajaxcomments AJAX handler. Normally, nonces are used to validate that requests originate from legitimate users and prevent CSRF attacks. However, in this case, the plugin incorrectly rejects requests with valid nonces and accepts those with missing or invalid nonces, effectively inverting the intended security check. This flaw allows an unauthenticated attacker to craft a malicious request that, when a logged-in user clicks a link or visits a page, submits comments on their behalf without their consent. The attack requires the plugin's template mode to be enabled, which is a specific configuration setting. The vulnerability impacts the integrity of user-generated content by enabling unauthorized comment submissions but does not affect confidentiality or availability directly. The CVSS 3.1 score of 4.3 reflects the network attack vector, low attack complexity, no privileges required, user interaction needed, and limited impact on integrity only. No public exploits have been reported, but the vulnerability poses a risk to WordPress sites using this plugin, especially those with active user sessions and template mode enabled. The lack of an official patch at the time of reporting means users must rely on configuration changes or mitigations until an update is released.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized comment submissions on WordPress sites using the AMP for WP plugin, potentially damaging the integrity and trustworthiness of published content. Attackers could use this to inject spam, phishing links, or misleading information, harming brand reputation and user trust. While the vulnerability does not directly compromise sensitive data or system availability, the manipulation of user-generated content can have downstream effects such as SEO penalties, increased moderation overhead, and potential legal or compliance issues related to content control. Organizations relying on WordPress for customer engagement, marketing, or communications in Europe should be particularly vigilant. The risk is heightened in environments where the plugin's template mode is enabled and where users have active authenticated sessions, as these conditions enable exploitation. Although no known exploits are currently in the wild, the public disclosure increases the likelihood of future attacks, especially targeting high-traffic or high-profile European websites.

Mitigation Recommendations

Immediate mitigation steps include disabling the plugin's template mode to prevent the vulnerable AJAX handler from processing requests. Administrators should also consider temporarily disabling or restricting access to the amp_theme_ajaxcomments AJAX endpoint, for example by implementing web application firewall (WAF) rules that block suspicious requests or require additional verification. Monitoring and logging AJAX comment submissions can help detect anomalous activity indicative of exploitation attempts. Organizations should keep abreast of official patches or updates from the plugin vendor and apply them promptly once available. Additionally, educating users about the risks of clicking unsolicited links while logged into administrative or user accounts can reduce the likelihood of successful CSRF attacks. Employing Content Security Policy (CSP) headers and SameSite cookie attributes can further mitigate CSRF risks by restricting cross-origin requests. Finally, regular security audits of WordPress plugins and configurations can help identify and remediate similar vulnerabilities proactively.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-10T16:39:16.138Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695de67ca55ed4ed995516f1

Added to database: 1/7/2026, 4:52:12 AM

Last enriched: 1/14/2026, 3:37:07 PM

Last updated: 2/7/2026, 9:32:17 AM

Views: 54

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats