CVE-2025-9378
BaseFortify
Publication date: 2025-09-03
Last updated on: 2025-09-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| themehunk | vayu_blocks | * |
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?
The vulnerability in the Vayu Blocks β Website Builder for the Block Editor WordPress plugin is a Stored Cross-Site Scripting (XSS) issue affecting the Lottie block. It occurs because the plugin does not properly sanitize or escape multiple attributes in the Lottie block, allowing authenticated users with Contributor-level access or higher to inject malicious scripts. These scripts are then stored and executed whenever any user views the affected page, potentially compromising user security. [2]
How can this vulnerability impact me? :
This vulnerability can allow attackers with Contributor-level access or above to inject arbitrary malicious scripts into pages using the Lottie block. When other users visit these pages, the injected scripts execute in their browsers, potentially leading to theft of sensitive information, session hijacking, or other malicious actions. This can compromise the security and integrity of your website and its users.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by inspecting WordPress sites using the Vayu Blocks plugin versions up to 1.3.9 for the presence of malicious scripts injected via the Lottie block attributes. Since the vulnerability involves Stored Cross-Site Scripting (XSS) through insufficient sanitization of attributes like 'lottieUrl' or 'link', detection can involve searching for suspicious or unexpected script tags or event handlers in pages containing Lottie blocks. On the system, you can check the installed plugin version to see if it is vulnerable. For example, use WP-CLI to check the plugin version: `wp plugin get vayu-blocks --field=version`. To detect injected scripts in the database, you might run SQL queries to search for suspicious content in post meta or post content fields related to Lottie blocks. Network detection could involve monitoring HTTP responses for unexpected script injections in pages with Lottie blocks. However, no specific commands are provided in the resources. [2]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Vayu Blocks β Website Builder for the Block Editor plugin to version 1.3.10 or later, as the update involves extensive file changes likely addressing the vulnerability. Until the update is applied, restrict Contributor-level and higher user access to trusted users only, as the vulnerability requires authenticated users with at least Contributor privileges to exploit. Additionally, consider reviewing and sanitizing any existing Lottie block content for malicious scripts. Applying security plugins or web application firewalls that can detect and block XSS attempts may also help mitigate risk temporarily. [1]