dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-41930

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-06
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vvveb before version 1.0.8.2 bundles a phpMyAdmin container via docker-compose-apache.yaml that contains hard-coded database credentials. Attackers can access the phpMyAdmin port without authentication and obtain full read/write access to the application's database, exposing administrator password hashes, customer PII, and order data.

MitigationUpgrade to Vvveb 1.0.8.2 or later, immediately rotate all exposed credentials, implement authentication for phpMyAdmin, force password resets for all administrator accounts, and audit for unauthorized database access or account modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Vvveb installation version
    Locate the Vvveb installation directory and check the version file or composer.json, or log into the admin panel and look for the version number in the system information or about section
    Affected if The installed version is earlier than 1.0.8.2
  2. Locate docker-compose-apache.yaml
    Search the Vvveb installation directory for a file named docker-compose-apache.yaml which should be present in the root or deployment folder of the application
    Affected if The docker-compose-apache.yaml file exists in the Vvveb deployment
  3. Inspect docker-compose-apache.yaml for phpMyAdmin configuration
    Open docker-compose-apache.yaml and examine its contents for a phpMyAdmin service definition, noting the image tag and any associated configuration
    Affected if The file contains a phpMyAdmin service definition
  4. Check for hard-coded database credentials
    Within docker-compose-apache.yaml, look for hard-coded values in environment variables such as PMA_HOST, PMA_USER, PMA_PASSWORD, or similar that contain static credentials rather than referencing environment variables
    Affected if Environment variables in the phpMyAdmin service contain hard-coded username and password values instead of variable references
  5. Verify phpMyAdmin port exposure
    Check the docker-compose-apache.yaml for port mappings that expose phpMyAdmin (typically port 8080 or 80) to external interfaces (0.0.0.0) rather than localhost only, or run 'docker ps' to confirm the container is binding to an external interface
    Affected if The phpMyAdmin container port is bound to 0.0.0.0 or all interfaces rather than 127.0.0.1 only

A user is affected if they are running Vvveb version earlier than 1.0.8.2 with the docker-compose-apache.yaml file containing an exposed phpMyAdmin service with hard-coded credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Vvveb 1.0.8.2 or later, immediately rotate all exposed credentials, implement authentication for phpMyAdmin, force password resets for all administrator accounts, and audit for unauthorized database access or account modifications.

Recommended fix Moderate confidence

Vvveb version 1.0.8.2 or later

  1. Upgrade Vvveb to version 1.0.8.2 or later which removes the hardcoded credentials from docker-compose-apache.yaml
  2. If upgrading is not immediately possible, edit docker-compose-apache.yaml and remove or secure the hardcoded phpMyAdmin credentials
  3. Change all database credentials (root password, database user passwords) that were exposed via the hardcoded configuration
  4. Review and restrict network access to the phpMyAdmin container to prevent unauthorized external access
  5. Rotate any administrator passwords and API keys that may have been stored in the compromised database

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41930 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data