CVE-2025-71177
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-01-29
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| lavalite | lavalite | to 10.1.0 (inc) |
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?
CVE-2025-71177 is a stored cross-site scripting (XSS) vulnerability in LavaLite CMS versions up to 10.1.0. Authenticated users can inject malicious HTML or JavaScript code into the 'Name' or 'Description' fields when creating packages. This malicious code is stored and later executed in the browsers of other users who view the package search results, leading to potential session hijacking, credential theft, and unauthorized actions within the victim's context. [2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute arbitrary JavaScript code in your browser when viewing package search results. This can lead to session hijacking, theft of credentials, defacement, or unauthorized actions performed on your behalf within the affected web application. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for stored malicious scripts in the 'Name' or 'Description' fields of packages within the LavaLite CMS. For example, you can perform a search query for suspicious script tags like <script> in the package search functionality. Since the vulnerability involves stored cross-site scripting, inspecting package entries for injected JavaScript code is key. There are no specific commands provided in the resources, but manual inspection or automated scanning of package data for script tags or suspicious HTML/JavaScript content in these fields is recommended. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or reviewing authenticated user input in the package creation process, especially in the 'Name' and 'Description' fields, to prevent injection of malicious scripts. Applying proper output encoding or sanitization on these fields before rendering search results is critical. Since no official patch or mitigation details are provided, limiting user privileges, monitoring package content for suspicious scripts, and educating users about the risk can help reduce exposure until a fix is available. [2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.