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-62096: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in WPFactory Maximum Products per User for WooCommerce

0
Medium
VulnerabilityCVE-2025-62096cvecve-2025-62096cwe-79
Published: Wed Dec 31 2025 (12/31/2025, 13:12:18 UTC)
Source: CVE Database V5
Vendor/Project: WPFactory
Product: Maximum Products per User for WooCommerce

Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPFactory Maximum Products per User for WooCommerce allows Stored XSS.This issue affects Maximum Products per User for WooCommerce: from n/a through 4.4.2.

AI-Powered Analysis

AILast updated: 01/20/2026, 22:22:57 UTC

Technical Analysis

CVE-2025-62096 is a stored Cross-site Scripting (XSS) vulnerability identified in the WPFactory Maximum Products per User plugin for WooCommerce, a popular WordPress e-commerce extension. The vulnerability stems from improper neutralization of user-supplied input during web page generation, classified under CWE-79. This flaw allows an attacker with at least low-level privileges (PR:L) to inject malicious scripts that are stored and later executed in the context of other users who view the affected pages, requiring user interaction (UI:R). The vulnerability affects all versions up to 4.4.2, with no patch currently available. The CVSS 3.1 base score is 6.5, reflecting a medium severity due to network attack vector (AV:N), low attack complexity (AC:L), and the potential for partial impact on confidentiality, integrity, and availability (C:L/I:L/A:L). The scope is changed (S:C), meaning the vulnerability can affect resources beyond the initially vulnerable component. Although no known exploits are reported in the wild, the stored XSS nature poses risks such as session hijacking, defacement, or injection of malicious payloads that can compromise user data or site integrity. The plugin’s role in managing product purchase limits per user makes it a critical component in WooCommerce stores, potentially affecting customer experience and trust if exploited.

Potential Impact

For European organizations, especially those operating e-commerce platforms based on WooCommerce, this vulnerability can lead to unauthorized script execution in users’ browsers, resulting in theft of session cookies, redirection to malicious sites, or unauthorized actions performed on behalf of users. This compromises customer data confidentiality and can damage brand reputation. The integrity of product purchase limits and related business logic may be undermined, potentially enabling fraudulent transactions or abuse of purchase restrictions. Availability impacts may arise if attackers use the vulnerability to inject disruptive scripts causing site malfunction or downtime. Given the widespread use of WooCommerce in Europe’s online retail sector, the risk extends to numerous small and medium enterprises reliant on this plugin. The absence of known exploits currently reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability details are public.

Mitigation Recommendations

Organizations should immediately audit their WooCommerce installations to identify the presence of the WPFactory Maximum Products per User plugin and its version. Until an official patch is released, implement strict input validation and sanitization on all user inputs related to product purchase limits, ideally through custom code or security plugins that enforce content filtering. Employ Web Application Firewalls (WAFs) with rules targeting XSS payloads to block malicious requests. Limit user privileges to the minimum necessary to reduce the risk of exploitation by low-privilege attackers. Monitor logs and user activity for unusual behavior indicative of XSS exploitation attempts. Educate site administrators and users about the risks of clicking suspicious links or interacting with untrusted content. Once a patch becomes available, prioritize its deployment. Additionally, consider implementing Content Security Policy (CSP) headers to restrict script execution sources, mitigating the impact of potential XSS attacks.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-10-07T15:35:03.408Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69552525db813ff03eea367e

Added to database: 12/31/2025, 1:29:09 PM

Last enriched: 1/20/2026, 10:22:57 PM

Last updated: 2/4/2026, 11:54:46 PM

Views: 40

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