CVE-2026-0627: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
The AMP for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG file uploads in all versions up to, and including, 1.1.10. This is due to insufficient sanitization of SVG file content that only removes `<script>` tags while allowing other XSS vectors such as event handlers (onload, onerror, onmouseover), foreignObject elements, and SVG animation attributes. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts via malicious SVG file uploads that will execute whenever a user views the uploaded file.
AI Analysis
Technical Summary
CVE-2026-0627 is a stored cross-site scripting vulnerability identified in the AMP for WP – Accelerated Mobile Pages plugin for WordPress, affecting all versions up to and including 1.1.10. The vulnerability stems from insufficient sanitization of SVG file uploads. While the plugin removes <script> tags from uploaded SVG files, it fails to neutralize other XSS vectors such as event handler attributes (e.g., onload, onerror, onmouseover), foreignObject elements, and SVG animation attributes. This incomplete sanitization allows authenticated users with Author-level privileges or higher to upload crafted SVG files containing malicious JavaScript code. When other users view these SVG files, the embedded scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, or unauthorized actions within the WordPress environment. The vulnerability has a CVSS 3.1 base score of 6.4, indicating medium severity, with an attack vector over the network, low attack complexity, requiring privileges (Author or above), no user interaction, and a scope change due to affecting other users. No public exploits have been reported yet, but the vulnerability poses a significant risk to multi-author WordPress sites using this plugin. The root cause is the reliance on simplistic sanitization that only removes <script> tags without addressing other SVG-based XSS attack vectors. This vulnerability highlights the complexity of safely handling SVG content, which can embed executable code in multiple ways beyond script tags. Until a patch is available, administrators should consider disabling SVG uploads or implementing more robust sanitization mechanisms. The vulnerability was published on January 9, 2026, and assigned by Wordfence.
Potential Impact
For European organizations, especially those operating WordPress sites with multiple content authors or contributors, this vulnerability presents a tangible risk of cross-site scripting attacks that can compromise user sessions, steal credentials, or perform unauthorized actions on behalf of users. The stored nature of the XSS means that malicious payloads persist on the server and execute whenever the SVG file is viewed, potentially affecting administrators, editors, or site visitors. This can lead to reputational damage, data breaches, and disruption of web services. Organizations in sectors with high web presence such as media, e-commerce, education, and government are particularly vulnerable. The requirement for Author-level access limits exploitation to insiders or compromised accounts, but phishing or credential theft could facilitate this. The vulnerability does not affect availability but impacts confidentiality and integrity of user data and site content. Given the widespread use of WordPress and the AMP for WP plugin in Europe, the threat surface is significant. Attackers could leverage this vulnerability for targeted attacks against European entities or as part of broader campaigns.
Mitigation Recommendations
1. Immediately restrict or disable SVG file uploads in the WordPress media library until a secure patch is available. 2. Implement server-side SVG sanitization using specialized libraries that comprehensively remove all executable content, including event handlers, foreignObject elements, and animation attributes, not just <script> tags. 3. Enforce strict user role management to limit Author-level privileges only to trusted users and monitor for suspicious upload activity. 4. Use Content Security Policy (CSP) headers to restrict script execution contexts and reduce the impact of potential XSS payloads. 5. Regularly audit and monitor uploaded media files for suspicious SVG content. 6. Keep the AMP for WP plugin updated and apply security patches promptly once released. 7. Educate content authors about the risks of uploading untrusted SVG files and encourage use of safer image formats. 8. Consider implementing Web Application Firewalls (WAF) with rules targeting SVG-based XSS attempts. 9. Review and harden WordPress security configurations to minimize privilege escalation risks. 10. Conduct penetration testing focusing on SVG upload vectors to validate mitigation effectiveness.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden
CVE-2026-0627: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
Description
The AMP for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG file uploads in all versions up to, and including, 1.1.10. This is due to insufficient sanitization of SVG file content that only removes `<script>` tags while allowing other XSS vectors such as event handlers (onload, onerror, onmouseover), foreignObject elements, and SVG animation attributes. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts via malicious SVG file uploads that will execute whenever a user views the uploaded file.
AI-Powered Analysis
Technical Analysis
CVE-2026-0627 is a stored cross-site scripting vulnerability identified in the AMP for WP – Accelerated Mobile Pages plugin for WordPress, affecting all versions up to and including 1.1.10. The vulnerability stems from insufficient sanitization of SVG file uploads. While the plugin removes <script> tags from uploaded SVG files, it fails to neutralize other XSS vectors such as event handler attributes (e.g., onload, onerror, onmouseover), foreignObject elements, and SVG animation attributes. This incomplete sanitization allows authenticated users with Author-level privileges or higher to upload crafted SVG files containing malicious JavaScript code. When other users view these SVG files, the embedded scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, or unauthorized actions within the WordPress environment. The vulnerability has a CVSS 3.1 base score of 6.4, indicating medium severity, with an attack vector over the network, low attack complexity, requiring privileges (Author or above), no user interaction, and a scope change due to affecting other users. No public exploits have been reported yet, but the vulnerability poses a significant risk to multi-author WordPress sites using this plugin. The root cause is the reliance on simplistic sanitization that only removes <script> tags without addressing other SVG-based XSS attack vectors. This vulnerability highlights the complexity of safely handling SVG content, which can embed executable code in multiple ways beyond script tags. Until a patch is available, administrators should consider disabling SVG uploads or implementing more robust sanitization mechanisms. The vulnerability was published on January 9, 2026, and assigned by Wordfence.
Potential Impact
For European organizations, especially those operating WordPress sites with multiple content authors or contributors, this vulnerability presents a tangible risk of cross-site scripting attacks that can compromise user sessions, steal credentials, or perform unauthorized actions on behalf of users. The stored nature of the XSS means that malicious payloads persist on the server and execute whenever the SVG file is viewed, potentially affecting administrators, editors, or site visitors. This can lead to reputational damage, data breaches, and disruption of web services. Organizations in sectors with high web presence such as media, e-commerce, education, and government are particularly vulnerable. The requirement for Author-level access limits exploitation to insiders or compromised accounts, but phishing or credential theft could facilitate this. The vulnerability does not affect availability but impacts confidentiality and integrity of user data and site content. Given the widespread use of WordPress and the AMP for WP plugin in Europe, the threat surface is significant. Attackers could leverage this vulnerability for targeted attacks against European entities or as part of broader campaigns.
Mitigation Recommendations
1. Immediately restrict or disable SVG file uploads in the WordPress media library until a secure patch is available. 2. Implement server-side SVG sanitization using specialized libraries that comprehensively remove all executable content, including event handlers, foreignObject elements, and animation attributes, not just <script> tags. 3. Enforce strict user role management to limit Author-level privileges only to trusted users and monitor for suspicious upload activity. 4. Use Content Security Policy (CSP) headers to restrict script execution contexts and reduce the impact of potential XSS payloads. 5. Regularly audit and monitor uploaded media files for suspicious SVG content. 6. Keep the AMP for WP plugin updated and apply security patches promptly once released. 7. Educate content authors about the risks of uploading untrusted SVG files and encourage use of safer image formats. 8. Consider implementing Web Application Firewalls (WAF) with rules targeting SVG-based XSS attempts. 9. Review and harden WordPress security configurations to minimize privilege escalation risks. 10. Conduct penetration testing focusing on SVG upload vectors to validate mitigation effectiveness.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-01-05T22:04:46.579Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6960bf3fecefc3cd7c1371c8
Added to database: 1/9/2026, 8:41:35 AM
Last enriched: 1/9/2026, 8:56:05 AM
Last updated: 1/9/2026, 11:46:25 PM
Views: 23
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-15501: OS Command Injection in Sangfor Operation and Maintenance Management System
CriticalCVE-2026-22584: CWE-94 Improper Control of Generation of Code ('Code Injection') in Salesforce Uni2TS
UnknownCVE-2025-62487: The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. in Palantir com.palantir.acme:gotham-default-apps-bundle
LowCVE-2025-46299: Processing maliciously crafted web content may disclose internal states of the app in Apple tvOS
MediumCVE-2025-46298: Processing maliciously crafted web content may lead to an unexpected process crash in Apple tvOS
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.