Skip to content
OpenAdvisories

Weakness (CWE)

CWE-620: Unverified Password Change

Base Draft

When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.

How to prevent it (2 mitigations)

  1. Architecture and Design

    When prompting for a password change, force the user to provide the original password in addition to the new password.

  2. Architecture and Design

    Do not use "forgotten password" functionality. But if you must, ensure that you are only providing information to the actual user, e.g. by using an email address or challenge question that the legitimate user already provided in the past; do not allow the current user to change this identity information until the correct password has been provided.

Source: MITRE CWE-620

All Critical High Medium Low Exploited only Public exploit

2 results · Clear filters · Feed

  • High 8.3
    CVE-2026-73292 Public exploit

    Semaphore UI: CSRF vulnerability on password change endpoint - No CSRF token or password confirmation

    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, a…

    semaphoreui semaphore github.com/semaphoreui/semaphore Go
  • High 8.2
    CVE-2025-22381 Public exploit

    Aggie 2.6.1 has a Host Header injection vulnerability in the forgot password functionality, allowing an attacker to res…