CVE-2026-34428 | givanz Vvveb up to 1.0.8.0 file URL getUrl server-side request forgery

VDB-358309 · CVE-2026-34428 · GCVE-0-2026-34428 GIVANZ VVVEB UP TO 1.0.8.0 FILE URL GETURL SERVER-SIDE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.8 $0-$5k 2.42+ Summaryinfo A vulnerability was found in givanz Vvveb up to 1.0.8.0. It has been rated as critical. The affected element is the function getUrl of the component file URL Handler. This manipulation causes server-side request forgery. The identification of this vulnerability is CVE-2026-34428. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised. Detailsinfo A vulnerability classified as critical was found in givanz Vvveb up to 1.0.8.0. Affected by this vulnerability is the function getUrl of the component file URL Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is: Vvveb prior to 1.0.8.1 contains a server-side request forgery vulnerability in the oEmbedProxy action of the editor/editor module where the url parameter is passed directly to getUrl() via curl without scheme or destination validation. Authenticated backend users can supply file:// URLs to read arbitrary files readable by the web server process or http:// URLs targeting internal network addresses to probe internal services, with response bodies returned directly to the caller. The weakness was shared by Hamed Kohi. The advisory is shared at github.com. This vulnerability is known as CVE-2026-34428 since 03/27/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. Upgrading to version 1.0.8.1 eliminates this vulnerability. Applying the patch 2d356844f37819bf771e7cd5e12a8686975e0b2b is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Vendor givanz Name Vvveb Version 1.0.0 1.0.1 1.0.2 1.0.3 1.0.4 1.0.5 1.0.6 1.0.7 1.0.8.0 Website Product: https://github.com/givanz/Vvveb/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 7.0 VulDB Meta Temp Score: 6.8 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.7 CNA Vector (VulnCheck): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Server-side request forgery CWE: CWE-918 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Vvveb 1.0.8.1 Patch: 2d356844f37819bf771e7cd5e12a8686975e0b2b Timelineinfo 03/27/2026 CVE reserved 04/20/2026 +23 days Advisory disclosed 04/20/2026 +0 days VulDB entry created 04/20/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Researcher: Hamed Kohi Status: Confirmed CVE: CVE-2026-34428 (🔒) GCVE (CVE): GCVE-0-2026-34428 GCVE (VulDB): GCVE-100-358309 Entryinfo Created: 04/20/2026 16:56 Changes: 04/20/2026 16:56 (79) Complete: 🔍 Cache ID: 99:AA7:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸