CVE
Vvveb auth bypass in generateCookie() via PHP type juggling
Vvveb versions before 1.0.9.0 are affected, where cookie validation in generateCookie() uses loose comparison on MD5 hashes. Fixed in 1.0.9.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.9.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.0.9.0.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.56% · 47th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vvveb before 1.0.9.0 contains an authentication bypass vulnerability in generateCookie() in system/user/user.php that uses loose comparison to validate MD5 cookie hashes. Unauthenticated attackers can brute-force cookie values until the server's MD5 computation yields a 0e magic hash, then forge persistent cookies for account takeover.
Who should check
Teams running givanz Vvveb CMS versions before 1.0.9.0 (advisory lists 1.0.8.6 as affected, fixed in 1.0.8.7) with cookie-based user login
Read the source excerpt
“Vvveb before 1.0.9.0 contains an authentication bypass vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.0.9.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126377 (Vvveb before 1.0.9.0 Cookie Forgery via PHP Type Juggling in generateCookie()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126377 (entry last updated 2026-11-13):
Affected:
- givanz Vvveb: fixed in 1.0.9.0
Fixed versions: 1.0.9.0.
Conditions (all must be true for the bug to be hit):
- Vvveb versions before 1.0.9.0 (advisory lists affected version 1.0.8.6, patched in 1.0.8.7) (source: https://www.vulncheck.com/advisories/vvveb-before-1.0.9.0-cookie-forgery-via-php-type-juggling-in-generatecookie)
- Cookie validation via generateCookie() in system/user/user.php uses loose comparison (==) on MD5 hashes (source: https://www.vulncheck.com/advisories/vvveb-before-1.0.9.0-cookie-forgery-via-php-type-juggling-in-generatecookie)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126377 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126377 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/givanz/Vvveb/security/advisories/GHSA-p8w8-2rq6-wm2g
- https://www.vulncheck.com/advisories/vvveb-before-1.0.9.0-cookie-forgery-via-php-type-juggling-in-generatecookie
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126377
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126377"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- givanz Vvveb
fixed in 1.0.9.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126377
Is CVE-2026-126377 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The cookie check in generateCookie() compares MD5 hashes with loose (==) comparison, so a forged persistent cookie can pass validation and bypass authentication. The advisory says this can lead to account takeover.Source: vulncheck.com
Which versions are affected by CVE-2026-126377?
Vvveb: before 1.0.9.0.Source: cve.now feed data
Am I affected, and how do I check?
Vvveb versions before 1.0.9.0 are in scope, and the advisory lists 1.0.8.6 as an affected version. To check a installation, compare the installed Vvveb version with 1.0.9.0.Source: vulncheck.com
How do I fix CVE-2026-126377?
Upgrade Vvveb to 1.0.9.0 or later, which is the fixed version.Source: vulncheck.com