# CVE-2025-11029: givanz Vvveb cross-site request forgery

> Remote attackers can perform cross-site request forgery attacks against Vvveb CMS, potentially modifying data or bypassing security controls.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-x68v-g3v3-vr3p

## What is CVE-2025-11029?

CVE-2025-11029 is a medium-severity vulnerability in givanz Vvveb, published on 26 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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."

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-11029?

It affects 1 product.


Products: Vvveb Vvveb.

## How do I fix CVE-2025-11029?

No fix has been published for CVE-2025-11029 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11029 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11029 exists.

## Other vulnerabilities in givanz Vvveb

- [CVE-2025-44022](https://insights.sbomify.com/CVE-2025-44022/): Code injection in n/a (critical 9.8)
- [CVE-2025-11028](https://insights.sbomify.com/CVE-2025-11028/): givanz Vvveb Image information disclosure (medium 6.9)
- [CVE-2025-12203](https://insights.sbomify.com/CVE-2025-12203/): givanz Vvveb Code Editor functions.php sanitizeFileName path traversal (medium 5.3)
- [CVE-2025-9728](https://insights.sbomify.com/CVE-2025-9728/): givanz Vvveb login.tpl cross site scripting (medium 5.3)
- [CVE-2025-9397](https://insights.sbomify.com/CVE-2025-9397/): givanz Vvveb media.php unrestricted upload (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11029 and fix it if it is affected.

What it is: CVE-2025-11029 is a medium-severity vulnerability in givanz Vvveb, published on 26 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11029 exists.

Affected product: givanz Vvveb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11029/ (Markdown: https://insights.sbomify.com/CVE-2025-11029/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11029
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11029
- OSV: https://osv.dev/vulnerability/CVE-2025-11029

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11029/
Summaries are generated and may contain mistakes; the official description above is the record.