Skip to main content
VulnerabilityPublished

CVE-2025-11029: givanz Vvveb · Cross-Site Request Forgery

Affects givanz VvvebSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
givanz VvvebAffected
  • =1.0.7.0
  • =1.0.7.1
  • =1.0.7.2
Fixed in–

AI-suggested

European organizations should immediately upgrade to the fixed version of givanz Vvveb once it is released on GitHub, as indicated by the maintainer. Until the patch is applied, organizations can implement several practical mitigations: 1) Employ anti-CSRF tokens in all state-changing requests within applications using Vvveb to ensure requests are legitimate. 2) Enforce strict SameSite cookie attributes (e.g., SameSite=Lax or Strict) to reduce the risk of CSRF attacks via cross-site requests. 3) Educate users about the risks of clicking unknown or suspicious links, especially when authenticated to sensitive applications. 4) Monitor web application logs for unusual or unexpected state-changing requests that could indicate attempted exploitation. 5) Use Content Security Policy (CSP) headers to restrict the sources of executable scripts and reduce the attack surface. 6) If feasible, implement multi-factor authentication (MFA) to add an additional layer of security, although it does not directly prevent CSRF, it can limit the impact of compromised sessions. These measures, combined with timely patching, will significantly reduce the risk posed by this vulnerability.

Description

A weakness has been identified in givanz Vvveb up to 1.0.7.2. This vulnerability affects unknown code. Executing manipulation can lead to cross-site request forgery. The attack can be executed remotely. The exploit has been made available to the public and could be exploited. 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."

References

Community reviews

Loading reviews…