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-6255: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in plugincy Dynamic AJAX Product Filters for WooCommerce

0
Medium
VulnerabilityCVE-2025-6255cvecve-2025-6255cwe-79
Published: Thu Aug 28 2025 (08/28/2025, 06:42:35 UTC)
Source: CVE Database V5
Vendor/Project: plugincy
Product: Dynamic AJAX Product Filters for WooCommerce

Description

The Dynamic AJAX Product Filters for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and including, 1.3.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 16:11:12 UTC

Technical Analysis

CVE-2025-6255 is a stored cross-site scripting vulnerability identified in the Dynamic AJAX Product Filters for WooCommerce plugin for WordPress, affecting all versions up to and including 1.3.7. The vulnerability stems from insufficient sanitization and escaping of the 'className' parameter during web page generation, classified under CWE-79. Authenticated attackers with Contributor-level privileges or higher can inject arbitrary JavaScript code into pages rendered by the plugin. Because the malicious script is stored persistently, it executes every time a user accesses the infected page, potentially compromising user sessions, stealing cookies, or performing unauthorized actions on behalf of users. The vulnerability has a CVSS 3.1 base score of 6.4, indicating medium severity, with an attack vector of network, low attack complexity, requiring privileges but no user interaction, and impacting confidentiality and integrity with a scope change. No public exploits have been reported yet, but the vulnerability poses a significant risk given the widespread use of WooCommerce and the plugin in e-commerce environments. The root cause is the failure to properly neutralize input before incorporating it into the HTML output, allowing script injection. The plugin developer has not yet released a patch, so mitigation requires immediate attention from site administrators.

Potential Impact

This vulnerability can lead to unauthorized script execution in the context of the affected website, enabling attackers to hijack user sessions, steal sensitive information such as cookies or credentials, deface web content, or perform actions on behalf of legitimate users. Since the attack requires authenticated access at Contributor level or above, it primarily threatens multi-user WordPress environments where users have elevated privileges. The impact is significant for e-commerce sites using WooCommerce with this plugin, as attackers could manipulate product filters or user interactions, potentially undermining customer trust and causing reputational damage. The scope of affected systems is broad due to WooCommerce's global popularity, and the vulnerability affects confidentiality and integrity but not availability. Although no known exploits are currently active, the medium severity rating and ease of exploitation by authenticated users make it a credible threat that could be leveraged in targeted attacks or insider threat scenarios.

Mitigation Recommendations

1. Immediately upgrade the Dynamic AJAX Product Filters for WooCommerce plugin to a patched version once released by the vendor. 2. Until a patch is available, restrict Contributor-level and higher privileges to trusted users only, minimizing the risk of malicious script injection. 3. Implement a Web Application Firewall (WAF) with custom rules to detect and block suspicious payloads targeting the 'className' parameter. 4. Conduct regular security audits and code reviews of custom plugins and themes to ensure proper input validation and output encoding. 5. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on the website. 6. Monitor logs for unusual activities or changes to product filter pages that could indicate exploitation attempts. 7. Educate site administrators and users with elevated privileges about the risks of XSS and safe content management practices. 8. Consider temporarily disabling the plugin if immediate patching or mitigation is not feasible and the risk is deemed high.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-06-18T21:26:31.373Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68affb97ad5a09ad006a13c5

Added to database: 8/28/2025, 6:47:51 AM

Last enriched: 2/27/2026, 4:11:12 PM

Last updated: 3/22/2026, 1:47:38 PM

Views: 127

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses