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-4212: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wpwham Checkout Files Upload for WooCommerce

0
High
VulnerabilityCVE-2025-4212cvecve-2025-4212cwe-79
Published: Tue Nov 18 2025 (11/18/2025, 09:27:35 UTC)
Source: CVE Database V5
Vendor/Project: wpwham
Product: Checkout Files Upload for WooCommerce

Description

The Checkout Files Upload for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via file uploads in all versions up to, and including, 2.2.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in image files that will execute whenever a user accesses the injected page.

AI-Powered Analysis

AILast updated: 11/25/2025, 11:14:49 UTC

Technical Analysis

CVE-2025-4212 identifies a stored Cross-Site Scripting (XSS) vulnerability in the Checkout Files Upload for WooCommerce plugin for WordPress, affecting all versions up to and including 2.2.1. The vulnerability stems from insufficient sanitization of user-supplied input during file uploads and inadequate escaping of output when rendering uploaded files on web pages. Attackers can exploit this flaw by embedding malicious JavaScript payloads within image files uploaded through the plugin's checkout file upload feature. Because the vulnerability is stored XSS, the malicious script persists on the server and executes in the context of any user who views the infected page, potentially stealing session cookies, performing actions on behalf of users, or redirecting users to malicious sites. Notably, exploitation requires no authentication or user interaction, increasing the attack surface. The CVSS 3.1 score of 7.2 reflects a high severity due to network attack vector, low attack complexity, no privileges required, no user interaction, and a scope change indicating potential impact beyond the vulnerable component. The vulnerability affects confidentiality and integrity but not availability. No patches or known exploits are currently reported, but the public disclosure demands immediate attention from site administrators. The plugin is widely used in WooCommerce-based e-commerce sites, which handle sensitive customer and payment data, making this vulnerability particularly concerning.

Potential Impact

For European organizations, especially those operating e-commerce platforms using WooCommerce with the affected plugin, this vulnerability poses significant risks. Successful exploitation can lead to theft of user credentials, session hijacking, and unauthorized actions within the affected websites, undermining customer trust and potentially leading to data breaches involving personal and payment information. The stored nature of the XSS means that multiple users can be affected once the malicious payload is uploaded. This can result in reputational damage, regulatory penalties under GDPR for inadequate protection of personal data, and financial losses. The vulnerability's ease of exploitation without authentication increases the likelihood of automated attacks targeting vulnerable sites. Given the widespread use of WooCommerce in Europe, particularly in countries with mature e-commerce markets, the threat could impact a large number of businesses, including SMEs that may lack robust security practices.

Mitigation Recommendations

Immediate mitigation involves monitoring for plugin updates from the vendor and applying patches as soon as they become available. Until an official patch is released, organizations should consider disabling the Checkout Files Upload feature or the entire plugin if feasible. Implementing strict server-side validation to reject files containing suspicious content or scripts is critical. Employing Content Security Policy (CSP) headers can help mitigate the impact of XSS by restricting script execution sources. Web Application Firewalls (WAFs) should be configured to detect and block malicious payloads in file uploads and HTTP requests. Regular security audits and penetration testing focusing on file upload functionalities are recommended. Additionally, educating site administrators about the risks of untrusted file uploads and encouraging the use of security plugins that sanitize inputs can reduce exposure. Logging and monitoring for unusual upload activity or script execution can aid in early detection of exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-05-02T11:46:23.557Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691c3e34a312a743bb510bda

Added to database: 11/18/2025, 9:36:52 AM

Last enriched: 11/25/2025, 11:14:49 AM

Last updated: 1/8/2026, 12:43:13 PM

Views: 96

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