Semaphore UI: CSRF vulnerability on password change endpoint - No CSRF token or password confirmation
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 8.3epss 0.2%
from disclosure to weapon0 days
Published on NVDAug 12
1st PoCJul 29
exploitation probability
0.2%top 91% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
Semaphore UI is a web interface for managing DevOps tools. Prior to 2.18.21, the /api/users/{id}/password endpoint accepts a cross-site request using the authenticated user's semaphore session cookie without CSRF protection or current-password confirmation, allowing an unauthenticated attacker to change an administrator's or another user's password after user interaction. This issue is fixed in version 2.18.21.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
Affected products
semaphoreui · semaphorepublic PoCs found — 1
githubgithub.com/CamilleGR/CVE-2026-73292★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/semaphoreui/semaphore/commit/2d6e2e3eb10e8bf688e2ab59609b909a012fad4chttps://github.com/semaphoreui/semaphore/commit/c59c3dc9035badcbf0609c7d35679c06e590a956https://github.com/semaphoreui/semaphore/releases/tag/v2.18.21https://github.com/semaphoreui/semaphore/security/advisories/GHSA-8cj9-r88m-8945