# CVE-2026-41930: Vvveb < 1.0.8.2 Hard-coded Credentials Information Disclosure via phpMyAdmin

> Hard-coded credentials in Vvveb's Docker configuration allow attackers to access phpMyAdmin, leading to database exposure and account takeover.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-g38h-mr9p-fjmf

## What is CVE-2026-41930?

CVE-2026-41930 is a critical vulnerability in givanz Vvveb, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vvveb before version 1.0.8.2 contains a hard-coded credentials vulnerability in its docker-compose-apache.yaml configuration that allows unauthenticated attackers to access the bundled phpMyAdmin container with pre-configured database credentials. Attackers can connect to the phpMyAdmin port to gain unrestricted read and write access to the entire Vvveb database, including administrator password hashes, customer personally identifiable information, and order data, enabling account takeover and data manipulation.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-41930 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41930 is a critical vulnerability in givanz Vvveb, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41930 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-41930/ (Markdown: https://insights.sbomify.com/CVE-2026-41930/index.md)
```

## Sources

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

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