CVE-2025-4566
BaseFortify
Publication date: 2025-07-29
Last updated on: 2025-07-29
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dompurify | dompurify | 3.2.3 |
| elementor | website_builder | 3.28.4 |
| elementor | website_builder | * |
| elementor | website_builder | 3.30.2 |
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 Elementor Website Builder plugin for WordPress, specifically in the Text Path widget. It arises from insufficient input sanitization and output escaping of the data-text DOM element attribute. Authenticated users with Contributor-level access or higher can inject arbitrary web scripts into pages. These scripts execute whenever a user views the injected page, but the attack only affects Chrome and Edge browsers.
How can this vulnerability impact me? :
The vulnerability allows attackers with Contributor-level access or above to inject malicious scripts into website pages. When other users visit these pages using Chrome or Edge browsers, the injected scripts execute, potentially leading to unauthorized actions such as stealing user data, session hijacking, or defacement of the website. This can compromise the security and integrity of the affected website 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 enables unauthorized script execution that could lead to data breaches or unauthorized access to personal or sensitive information. Such incidents may violate data protection requirements and result in legal and regulatory consequences.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying pages using the Elementor Website Builder plugin version 3.30.2 or earlier that include the Text Path widget with the data-text DOM element attribute. Since the vulnerability involves Stored Cross-Site Scripting (XSS) exploitable by authenticated users with Contributor-level access or higher, detection can involve scanning for injected scripts in page content, especially in SVG text paths. Commands to detect suspicious injected scripts could include using curl or wget to fetch page source and grep for suspicious <script> tags or event handlers in the data-text attribute. For example, you can use: 1) curl -s https://example.com/page | grep -i 'data-text' 2) curl -s https://example.com/page | grep -E '<script|onerror|onload|javascript:' 3) Use browser developer tools to inspect the DOM for unexpected script injections in the Text Path widget elements. Additionally, monitoring authenticated user activity for unusual content submissions may help detect exploitation attempts. Note that this vulnerability affects only Chrome/Edge browsers, so testing in those browsers may reveal execution of injected scripts.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the Elementor Website Builder plugin to version 3.30.3 or later, as this version includes extensive code changes likely addressing the security issue. The update involves significant modifications to PHP, JavaScript, and CSS files, indicating a comprehensive fix. Until the update is applied, restrict Contributor-level and higher user permissions to trusted users only, and monitor for suspicious activity. Additionally, consider disabling or limiting the use of the Text Path widget if possible. Applying web application firewall (WAF) rules to detect and block XSS payloads targeting the data-text attribute may also help mitigate risk. [1]