# CVE-2026-34427: Vvveb < 1.0.8.1 Privilege Escalation via admin/user/save

> Authenticated users can escalate to Super Administrator by modifying role_id in profile save requests, enabling remote code execution via plugin upload.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 20 Apr 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-fxgc-2fpp-hx5w

## What is CVE-2026-34427?

CVE-2026-34427 is a high-severity vulnerability in givanz Vvveb, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vvveb prior to 1.0.8.1 contains a privilege escalation vulnerability in the admin user profile save endpoint that allows authenticated users to modify privileged fields on their own profile. Attackers can inject role_id=1 into profile save requests to escalate to Super Administrator privileges, enabling plugin upload functionality for remote code execution.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

## Which versions are affected by CVE-2026-34427?


## How do I fix CVE-2026-34427?

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

## Is CVE-2026-34427 being exploited?

There is no known exploitation of CVE-2026-34427 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34427 and fix it if it is affected.

What it is: CVE-2026-34427 is a high-severity vulnerability in givanz Vvveb, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34427 in the wild and no public exploit code.

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-2026-34427/ (Markdown: https://insights.sbomify.com/CVE-2026-34427/index.md)
```

## Sources

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

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