CVE-2025-8394
BaseFortify
Publication date: 2025-09-17
Last updated on: 2025-09-17
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| productive_minds | productive_style | 1.1.25 |
| productive_minds | productive_style | 1.1.23 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Productive Style plugin for WordPress. It occurs in the plugin's display_productive_breadcrumb shortcode due to insufficient input sanitization and output escaping on user-supplied attributes. Authenticated attackers with contributor-level access or higher can inject arbitrary web scripts into pages. These scripts execute whenever any user accesses the injected page, potentially compromising user interactions and data.
How can this vulnerability impact me? :
The vulnerability allows attackers with contributor-level access or above to inject malicious scripts into pages viewed by other users. This can lead to unauthorized actions performed on behalf of users, theft of sensitive information such as cookies or session tokens, defacement of website content, or distribution of malware. It compromises the integrity and security of the affected WordPress site and its users.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively impact compliance with standards like GDPR and HIPAA because it may lead to unauthorized access or disclosure of personal or sensitive data through malicious script execution. Organizations must ensure proper input validation and output escaping to protect user data and maintain compliance. Failure to address such vulnerabilities could result in data breaches and regulatory penalties.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately update the Productive Style plugin for WordPress to a version later than 1.1.23 where the issue is fixed. Additionally, restrict contributor-level access and above to trusted users only, as the vulnerability requires authenticated users with such privileges to exploit. Consider implementing additional input sanitization and output escaping measures if you maintain the plugin code.