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-8394: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in productiveminds Productive Style – Optimisations & Content Publishing Support

0
Medium
VulnerabilityCVE-2025-8394cvecve-2025-8394cwe-79
Published: Wed Sep 17 2025 (09/17/2025, 01:49:14 UTC)
Source: CVE Database V5
Vendor/Project: productiveminds
Product: Productive Style – Optimisations & Content Publishing Support

Description

The Productive Style plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's display_productive_breadcrumb shortcode in all versions up to, and including, 1.1.23 due to insufficient input sanitization and output escaping on user supplied attributes. 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/26/2026, 17:04:48 UTC

Technical Analysis

CVE-2025-8394 is a stored cross-site scripting vulnerability identified in the Productive Style – Optimisations & Content Publishing Support plugin for WordPress. The vulnerability exists due to improper neutralization of input during web page generation, specifically within the display_productive_breadcrumb shortcode. This shortcode fails to adequately sanitize and escape user-supplied attributes, allowing authenticated users with contributor-level permissions or higher to inject arbitrary JavaScript code into pages. When other users access these pages, the injected scripts execute in their browsers, potentially compromising user sessions, stealing cookies, or performing actions on behalf of the victim. The vulnerability affects all versions up to and including 1.1.23. The CVSS 3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, and privileges required but no user interaction needed. The scope is changed due to the potential impact on other users viewing the injected content. No public exploits have been reported yet. The vulnerability highlights the importance of proper input validation and output encoding in WordPress plugins, especially those that allow user-generated content or shortcode attributes. The lack of a patch link suggests that a fix may be pending or users must implement manual mitigations.

Potential Impact

This vulnerability allows authenticated users with contributor-level access or higher to inject malicious scripts that execute in the browsers of any users viewing the affected pages. The impact includes potential theft of session cookies, enabling account takeover, defacement of website content, or redirection to malicious sites. Since WordPress powers a significant portion of websites globally, exploitation could lead to widespread compromise of sites using the vulnerable plugin. The attack requires authentication but no user interaction, increasing the risk within organizations that allow multiple contributors. The integrity and confidentiality of user data and site content are at risk, though availability is not directly impacted. The scope is significant because injected scripts can affect all visitors to compromised pages, potentially leading to reputational damage and loss of user trust for affected organizations.

Mitigation Recommendations

Organizations should immediately audit their WordPress installations to identify the presence of the Productive Style plugin and verify the version in use. Until an official patch is released, administrators should restrict contributor-level access to trusted users only and consider temporarily disabling the plugin or the vulnerable shortcode to prevent exploitation. Implementing a Web Application Firewall (WAF) with rules to detect and block suspicious script injections in shortcode attributes can provide additional protection. Site administrators should also enforce strict input validation and output encoding in custom code or plugin overrides if feasible. Monitoring logs for unusual activity related to shortcode usage and user actions can help detect exploitation attempts. Once a patch is available, prompt updating of the plugin is critical. Additionally, educating contributors about safe content practices and the risks of injecting scripts can reduce accidental exploitation.

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-07-30T20:16:12.785Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68ca1a3d571b2840ff0172ed

Added to database: 9/17/2025, 2:17:33 AM

Last enriched: 2/26/2026, 5:04:48 PM

Last updated: 3/25/2026, 4:50:56 AM

Views: 105

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