# CVE-2025-8517: givanz Vvveb session fixiation

> Attackers can hijack user sessions in Vvveb CMS, leading to account takeover; users should upgrade to the latest version.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2025
- **Updated:** 18 Aug 2025
- **Also known as:** GHSA-vp3r-hc2j-v8hr

## What is CVE-2025-8517?

CVE-2025-8517 is a medium-severity vulnerability in givanz Vvveb, published on 4 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in givanz Vvveb 1.0.6.1. Impacted is an unknown function. The manipulation results in session fixiation. The attack can be launched remotely. The exploit is now public and may be used. Upgrading to version 1.0.7 is recommended to address this issue. The patch is identified as d4b1e030066417b77d15b4ac505eed5ae7bf2c5e. You should upgrade the affected component.

Weakness: CWE-384 (Session Fixation)

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

It affects 1 product.


Products: Vvveb Vvveb.

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

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

## Is CVE-2025-8517 being exploited?

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

Public exploit code:

- CVE-2025-8517: Session Fixation in Vvveb CMS v1.0.6.1 (github_poc): https://github.com/helloandrewpaul/Session-Fixation-in-Vvveb-CMS-v1.0.6.1

## 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-11029](https://insights.sbomify.com/CVE-2025-11029/): givanz Vvveb cross-site request forgery (medium 5.3)
- [CVE-2025-9728](https://insights.sbomify.com/CVE-2025-9728/): givanz Vvveb login.tpl cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8517 is a medium-severity vulnerability in givanz Vvveb, published on 4 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8517 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-8517/ (Markdown: https://insights.sbomify.com/CVE-2025-8517/index.md)
```

## Sources

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

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