CVE-2025-11027
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-26

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was identified in givanz Vvveb up to 1.0.7.2. Affected by this issue is some unknown functionality of the component SVG File Handler. Such manipulation leads to cross site scripting. The attack may be launched remotely. The exploit is publicly available and might be used. Once again the project maintainer reacted very professional: "I accept the existence of these vulnerabilities. (...) I fixed the code to remove these vulnerabilities and will push the code to github and make a new release."
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-26
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-09-26
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
vvveb vvveb to 1.0.7.2 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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.
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the SVG File Handler component of givanz Vvveb up to version 1.0.7.2. It allows an attacker to perform cross-site scripting (XSS) attacks by manipulating SVG files. The attack can be launched remotely, potentially enabling an attacker to inject malicious scripts into the application.


How can this vulnerability impact me? :

The vulnerability can lead to cross-site scripting attacks, which may allow attackers to execute malicious scripts in the context of the affected application. This can result in unauthorized actions, data manipulation, or other malicious activities depending on the privileges of the user and the context in which the vulnerability is exploited.


What immediate steps should I take to mitigate this vulnerability?

The project maintainer has fixed the code to remove these vulnerabilities and will push the code to GitHub and make a new release. Immediate steps include updating to the fixed version once it is released. Until then, consider restricting access to the affected component and applying strict input validation or sanitization to mitigate cross-site scripting risks.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart