CWE-836Base

Use of Password Hash Instead of Password for Authentication

Incomplete in the CWE catalog · 16 CVEs mapped

16
CVEs mapped
7.2
Median CVSS
What it is

The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store.

Recent examples
6.5cvss
CVE-2026-44736

OpenProject: Relations API Filter Bypasses Visibility Scope, Leaking Cross-Project Work Package Subjects

OpenProject is open-source, web-based project management software. Prior to 17.4.0, the GET /api/v3/relations endpoint allows any authenticated user to retrieve relations — and the subject (title) of work packages they have no permission to view — by supplying an arbitrary work package ID in the involved, fromId, or toId filter. This bypasses the Relation.visible scope due to a flawed performance optimization in RelationQuery. This vulnerability is fixed in 17.4.0.

MEDIUMno explanation yet
0%
epss
8.1cvss
CVE-2026-9222

CVE-2026-9222 - HIGH Severity Vulnerability

Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 and prior only require the password hash when authenticating with backend services from the client. This could allow an attacker, who knows the hash, to authenticate and gain full access.

HIGHno explanation yet
0%
epss
4.3cvss
CVE-2026-40103

Vikunja's Scoped API tokens with projects.background permission can delete project backgrounds

Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.

MEDIUMno explanation yet
0%
epss
The record
Technical detail
CWE ID
CWE-836
Abstraction
Base
Structure
Simple
Status
Incomplete