CVE-2026-30269 | Doorman 0.1.0/1.0.2 /platform/user/ manage_users role access control
VulDBArchived Apr 20, 2026✓ Full text saved
A vulnerability was found in Doorman 0.1.0/1.0.2 . It has been rated as critical . Affected by this issue is the function manage_users of the file /platform/user/ . The manipulation of the argument role leads to improper access controls. This vulnerability is uniquely identified as CVE-2026-30269 . The attack is possible to be carried out remotely. No exploit exists.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358338 · CVE-2026-30269 · EUVD-2026-23902
DOORMAN 0.1.0/1.0.2 /PLATFORM/USER/ MANAGE_USERS ROLE ACCESS CONTROL
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.1 $0-$5k 5.78
Summaryinfo
A vulnerability categorized as critical has been discovered in Doorman 0.1.0/1.0.2. This affects the function manage_users of the file /platform/user/. The manipulation of the argument role results in access control. This vulnerability was named CVE-2026-30269. The attack may be performed from remote. There is no available exploit.
Detailsinfo
A vulnerability, which was classified as critical, was found in Doorman 0.1.0/1.0.2. Affected is the function manage_users of the file /platform/user/. The manipulation of the argument role with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Improper access control in Doorman v0.1.0 and v1.0.2 allows any authenticated user to update their own account role to a non-admin privileged role via /platform/user/{username}. The `role` field is accepted by the update model without a manage_users permission check for self-updates, enabling privilege escalation to high-privileged roles.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-30269 since 03/04/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/20/2026). This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-23902).
Productinfo
Name
Doorman
Version
0.1.0
1.0.2
CPE 2.3info
🔒
🔒
CPE 2.2info
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Access control
CWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/04/2026 CVE reserved
04/20/2026 +46 days Advisory disclosed
04/20/2026 +0 days VulDB entry created
04/20/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: github.com
Status: Not defined
CVE: CVE-2026-30269 (🔒)
GCVE (CVE): GCVE-0-2026-30269
GCVE (VulDB): GCVE-100-358338
EUVD: 🔒
Entryinfo
Created: 04/20/2026 19:58
Updated: 04/20/2026 23:33
Changes: 04/20/2026 19:58 (54), 04/20/2026 23:33 (1)
Complete: 🔍
Cache ID: 99:D8A:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸