/

CVE-2026-73292

Severity:

HIGH RISK

(8.3)

CSRF (CWE-352) in Semaphore UI Password Change Endpoint API

CVE-2026-73292

Deferred

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352, CWE-620

Impact:

Account Takeover

Severity:

HIGH RISK

(8.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A cross-site request forgery vulnerability in Semaphore UI allows a malicious website to submit a password-change request using a victim's authenticated Semaphore session.

After user interaction, an unauthenticated attacker may change an administrator's or another user's password because the endpoint does not require CSRF protection or confirmation of the current password.

Affected context

The issue occurs in Semaphore UI deployments where the password-change endpoint relies on the browser's session cookie but does not require a CSRF token or current-password confirmation. Exploitation generally depends on an authenticated user, potentially with administrative privileges, visiting attacker-controlled content while their Semaphore session remains active.

Exploit preconditions

  • Attack surface: Web-based password-change endpoint
  • Required access: No direct Semaphore authentication is required by the attacker, but a targeted victim must have an active authenticated session
  • Trigger point: A cross-site request to the user password-change endpoint
  • User interaction: The victim must access attacker-controlled or compromised content that causes the request to be sent
  • Why exploitation is possible: The server accepts the ambient session cookie without validating a CSRF token or requiring the current password

Why this happens

The vulnerability is caused by treating a state-changing password operation as valid when authenticated only by a browser session cookie. Without an unpredictable, origin-bound CSRF token and an additional reauthentication control, another site may cause the victim's browser to submit a request in the context of the existing session.

This maps primarily to CWE-352: Cross-Site Request Forgery. The absence of current-password confirmation also relates to CWE-620: Unverified Password Change, because a sensitive credential update can proceed without confirming knowledge of the existing password.

Potential impact

  • An attacker may change a victim's Semaphore password
  • A targeted administrator account could become unavailable to its owner
  • The attacker could gain account access if the new password is known to them
  • Administrative access may enable unauthorized management of connected DevOps tools
  • Recovery operations and incident response could be disrupted

General mitigation guidance

Mitigation generally focuses on protecting all state-changing browser requests, especially credential operations.

Common defensive patterns include:

  • Requiring unpredictable, session-bound CSRF tokens on password-change requests
  • Enforcing strict origin or referer validation as a complementary control
  • Requiring the current password or step-up authentication before changing credentials
  • Applying secure cookie attributes, including appropriate SameSite, Secure, and HttpOnly settings
  • Separating authentication, authorization, and reauthentication checks for sensitive actions
  • Limiting administrative privileges and providing reliable account-recovery controls
  • Avoiding password changes through cross-origin request methods or endpoints that accept ambient authentication without explicit verification

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules for state-changing endpoints that lack CSRF middleware or token validation
  • Code review checks for password, email, role, and access-token changes without reauthentication
  • Dynamic testing that submits sensitive requests from an unrelated origin while a test session is active
  • Web application firewall or gateway policies that validate origin metadata for sensitive operations
  • Monitoring for password changes that are followed by unusual login locations, session activity, or administrative actions
  • Automated security testing tools configured to assess CSRF protections and authentication requirements

Sources

SourceLink
github.comgithub.com/semaphoreui/semaphore/commit/2d6e2e3eb10e8bf688e2ab59609b909a012fad4c
github.comgithub.com/semaphoreui/semaphore/commit/c59c3dc9035badcbf0609c7d35679c06e590a956
github.comgithub.com/semaphoreui/semaphore/releases/tag/v2.18.21
github.comgithub.com/semaphoreui/semaphore/security/advisories/GHSA-8cj9-r88m-8945

Frequently asked

questions

Yes, in the sense that an attacker can host or compromise web content that causes a victim's browser to send the request. The attack still depends on victim interaction and an active authenticated Semaphore session.

Not necessarily. The victim's session supplies authentication to the endpoint, while the attacker supplies the cross-site request.

Protect the endpoint with robust CSRF defenses and require current-password confirmation or step-up authentication for password changes.

Treat credential and authorization changes as high-risk operations, enforce origin-bound request validation, use secure cookie settings, and test every state-changing endpoint for cross-origin request abuse.

Find out what's already
exploitable in your codebase.