CVE
Venueless plaintext password storage in admin profile form
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
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Admin users changing their profile details in the admin area profile form. Installations using OIDC login are not affected.
- 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
- 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? →
- 21/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? →
- Specific setups only
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Original 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.
Who should check
Teams running Venueless where admin users edit profile details without using OIDC login.
“Only admin users are impacted when changing their profile details.”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch5/5No fixed version listed; see vendor advisory
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 28 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Admin users changing their profile details in the admin area profile form. Installations using OIDC login are not affected.Workaround: The checked facts give no workaround. They state that installations using OIDC login are not affected.
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-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"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- venueless/venueless
Version range not reported
Evidence 3
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-130608
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: cve.now feed data
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: github.com
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: github.com
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: github.com
What if there's no patch?
The checked facts give no workaround. They state that installations using OIDC login are not affected.Source: github.com