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-11841: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wpsoul Greenshift – animation and page builder blocks

0
Medium
VulnerabilityCVE-2025-11841cvecve-2025-11841cwe-79
Published: Tue Nov 04 2025 (11/04/2025, 01:50:26 UTC)
Source: CVE Database V5
Vendor/Project: wpsoul
Product: Greenshift – animation and page builder blocks

Description

The Greenshift – animation and page builder blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Chart Data attributes in all versions up to, and including, 12.2.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

AILast updated: 11/11/2025, 08:20:45 UTC

Technical Analysis

CVE-2025-11841 is a stored Cross-Site Scripting (XSS) vulnerability identified in the Greenshift – animation and page builder blocks plugin for WordPress, affecting all versions up to and including 12.2.7. The root cause is insufficient sanitization and escaping of user-supplied input in the Chart Data attributes used by the plugin. This flaw allows an attacker with at least Contributor-level privileges to inject arbitrary JavaScript code into pages generated by the plugin. Because the malicious script is stored persistently, it executes in the context of any user who views the infected page, potentially compromising session tokens, cookies, or enabling further attacks such as privilege escalation or phishing. The vulnerability requires no user interaction beyond visiting the page but does require authenticated access, which limits the attack surface to users with contributor or higher roles. The CVSS 3.1 score of 6.4 reflects a medium severity, with low attack complexity and no user interaction needed, but requiring privileges. No known public exploits exist yet, but the vulnerability is publicly disclosed and should be considered a credible risk. The vulnerability impacts confidentiality and integrity but not availability. The plugin is widely used in WordPress sites for animation and page building, making it a relevant threat vector for websites relying on this plugin for content management and presentation.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of their web content and user data. Attackers exploiting this flaw can execute malicious scripts that may steal session cookies, enabling account takeover or unauthorized access to sensitive information. This can lead to data breaches, defacement of websites, or distribution of malware to site visitors, damaging organizational reputation and trust. Since the vulnerability requires contributor-level access, insider threats or compromised contributor accounts are a primary concern. Organizations with multiple contributors or less stringent access controls are at higher risk. The impact is particularly critical for organizations handling personal data under GDPR, as exploitation could lead to regulatory penalties due to data leakage. Additionally, compromised websites can be used as platforms for further attacks against customers or partners. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits following public disclosure.

Mitigation Recommendations

1. Monitor for and apply updates to the Greenshift plugin as soon as a security patch is released by the vendor. 2. Until a patch is available, restrict Contributor-level permissions to trusted users only and audit existing contributor accounts for suspicious activity. 3. Implement a Web Application Firewall (WAF) with rules to detect and block XSS payloads, particularly targeting the Chart Data attributes. 4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on affected sites. 5. Conduct regular security reviews and input validation audits on WordPress plugins and themes, focusing on user-supplied data handling. 6. Educate content contributors on security best practices to reduce the risk of accidental injection of malicious content. 7. Consider disabling or replacing the Greenshift plugin with alternatives that have a stronger security track record if immediate patching is not feasible.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-16T08:44:43.701Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690977c178d4f574c2b12d5f

Added to database: 11/4/2025, 3:49:21 AM

Last enriched: 11/11/2025, 8:20:45 AM

Last updated: 12/18/2025, 7:54:14 AM

Views: 65

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats