CVE-2026-130608 json
Plaintext password leak on email change form
published yesterday modified yesterday also EUVD-2026-127002 , GHSA-grh2-268g-c635
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository venueless/venueless. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-130608 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.1 | 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 |
Affected products
- pretix Venueless
Classification
- Weakness
-
- CWE-256 Plaintext Storage of a Password
References
-
github.com
/venueless/venueless/security/advisories/GHSA-grh2-268g-c635
vendor-advisory, advisory
Sources
- CVE List CVE-2026-130608
- NVD CVE-2026-130608
- Maintainer advisory GHSA-grh2-268g-c635
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of venueless/venueless published their own advisory on GitHub. Reviewed sources take precedence over it.