VulnerabilityPublished 26 Sep 2025

CVE-2025-11026: givanz Vvveb · Information Disclosure

Affects givanz VvvebSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
givanz Vvveb	Affected =1.0.7.0 =1.0.7.1 =1.0.7.2	Fixed in–

AI-suggested

European organizations should immediately identify all instances of givanz Vvveb versions 1.0.7.0 through 1.0.7.2 in their environments. They should prioritize upgrading to the fixed version once released by the maintainer on GitHub. Until patches are applied, organizations should restrict network access to the affected component, ideally limiting it to trusted internal networks and blocking external access via firewalls or network segmentation. Implementing strict input validation and monitoring for unusual access patterns to the Configuration File Handler component can help detect exploitation attempts. User awareness training to reduce the risk of social engineering that could trigger the required user interaction is also recommended. Additionally, organizations should audit configuration files and credentials potentially exposed by this vulnerability and rotate any sensitive keys or passwords as a precaution. Employing web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the vulnerable functionality can provide an additional layer of defense.

Description

A vulnerability was determined in givanz Vvveb up to 1.0.7.2. Affected by this vulnerability is an unknown functionality of the component Configuration File Handler. This manipulation causes information disclosure. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. 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."

Impact

For European organizations, the information disclosure vulnerability in givanz Vvveb could lead to leakage of sensitive configuration data, which might include credentials, API keys, or internal system details. This could facilitate further attacks such as privilege escalation, lateral movement, or targeted exploitation of other systems. Organizations using Vvveb in web development or content management may face risks to confidentiality, potentially impacting customer data privacy and compliance with regulations such as GDPR. While the vulnerability does not directly affect system integrity or availability, the indirect consequences of leaked information could be significant, especially in sectors handling sensitive or regulated data. The requirement for user interaction slightly reduces the risk but does not eliminate it, particularly in environments where social engineering or phishing could be leveraged. The public disclosure of exploit code increases the urgency for European entities to apply patches or mitigations promptly to prevent exploitation.

Summary

CVE-2025-11026 is a medium severity information disclosure vulnerability affecting the givanz Vvveb product versions 1.0.7.0 through 1.0.7.2. The vulnerability resides in an unspecified functionality of the Configuration File Handler component. This flaw allows an attacker to remotely manipulate the component to disclose sensitive information. The vulnerability can be exploited over the network without requiring authentication, though it does require some user interaction. The CVSS 4.0 vector indicates the attack complexity is low, no privileges are required, but user interaction is necessary. The impact is limited to confidentiality with no effect on integrity or availability. The project maintainer has acknowledged the vulnerability and committed to releasing a patched version on GitHub, demonstrating a responsible disclosure and remediation approach. No known exploits are currently active in the wild, but the exploit code has been publicly disclosed, increasing the risk of exploitation. The exact nature of the information disclosed is not detailed, but given the involvement of a configuration file handler, it could potentially expose configuration data, credentials, or other sensitive operational parameters. The vulnerability’s remote attack vector and low complexity make it a concern for organizations using affected versions of Vvveb, especially if the software is exposed to untrusted networks or the internet.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Sep 2025, 15:08 UTC

Technical details

References

Community reviews

Related threats