Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-639 (通过用户控制密钥绕过授权机制) — Vulnerability Class 1073

1073 vulnerabilities classified as CWE-639 (通过用户控制密钥绕过授权机制). AI Chinese analysis included.

CWE-639 represents an authorization bypass weakness where systems fail to validate that a user is permitted to access a resource identified by a user-controlled key. Attackers typically exploit this by manipulating identifiers, such as changing a numeric user ID in a URL or API parameter, to retrieve or modify another user’s private data. This insecure direct object reference allows unauthorized access without requiring authentication bypasses. Developers prevent this vulnerability by implementing robust server-side authorization checks that verify the requesting user’s permissions against the requested resource, rather than trusting client-supplied identifiers. Additionally, using indirect references or opaque tokens instead of predictable, sequential keys can mitigate the risk of enumeration and unauthorized access attempts.

MITRE CWE Description
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Retrieval of a user record occurs in the system based on some key value that is under user control. The key would typically identify a user-related record stored in the system and would be used to lookup that record for presentation to the user. It is likely that an attacker would have to be an authenticated user in the system. However, the authorization process would not properly check the data access operation to ensure that the authenticated user performing the operation has sufficient entitlements to perform the requested data access, hence bypassing any other authorization checks present in the system. For example, attackers can look at places where user specific data is retrieved (e.g. search screens) and determine whether the key for the item being looked up is controllable externally. The key may be a hidden field in the HTML form field, might be passed as a URL parameter or as an unencrypted cookie variable, then in each of these cases it will be possible to tamper with the key value. One manifestation of this weakness is when a system uses sequential or otherwise easily-guessable session IDs that would allow one user to easily switch to another user's session and read/modify their data.
Common Consequences (3)
Access ControlBypass Protection Mechanism
Access control checks for specific user data or functionality can be bypassed.
Access ControlGain Privileges or Assume Identity
Horizontal escalation of privilege is possible (one user can view/modify information of another user).
Access ControlGain Privileges or Assume Identity
Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.
Mitigations (3)
Architecture and DesignFor each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design, ImplementationMake sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and DesignUse encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
Examples (1)
The following code uses a parameterized statement, which escapes metacharacters and prevents SQL injection vulnerabilities, to construct and execute a SQL query that searches for an invoice matching the specified identifier [1]. The identifier is selected from a list of all invoices associated with the current authenticated user.
... conn = new SqlConnection(_ConnectionString); conn.Open(); int16 id = System.Convert.ToInt16(invoiceID.Text); SqlCommand query = new SqlCommand( "SELECT * FROM invoices WHERE id = @id", conn); query.Parameters.AddWithValue("@id", id); SqlDataReader objReader = objCommand.ExecuteReader(); ...
Bad · C#
CVE IDTitleCVSSSeverityPublished
CVE-2022-1425 WPQA < 5.2 - Subscriber+ Private Message Disclosure via IDOR — WPQA Builder Plugin 6.5 -2022-05-16
CVE-2022-23061 Shopizer - IDOR delete superadmin — Shopizer 6.5 Medium2022-05-01
CVE-2021-24800 DW Question & Answer Pro <= 1.3.4 - Arbitrary Comment Edition via IDOR — DW Question Answer Pro 4.3 -2022-04-25
CVE-2022-1165 Blackhole for Bad Bots < 3.3.2 - Arbitrary IP Address Blocking via IP Spoofing — Blackhole for Bad Bots 9.1 -2022-04-04
CVE-2022-0442 UsersWP < 1.2.3.1 - Subscriber+ User Avatar Override — UsersWP – User Registration & User Profile 4.3 -2022-03-07
CVE-2021-41111 Authorization Bypass Through User-Controlled Key in Rundeck — rundeck 6.4 Medium2022-02-28
CVE-2022-0691 Authorization Bypass Through User-Controlled Key in unshiftio/url-parse — unshiftio/url-parse 9.1 -2022-02-21
CVE-2022-0686 Authorization Bypass Through User-Controlled Key in unshiftio/url-parse — unshiftio/url-parse 9.1 -2022-02-20
CVE-2022-0639 Authorization Bypass Through User-Controlled Key in unshiftio/url-parse — unshiftio/url-parse 9.1 -2022-02-17
CVE-2022-0613 Authorization Bypass Through User-Controlled Key in medialize/uri.js — medialize/uri.js 7.4 -2022-02-16
CVE-2022-0512 Authorization Bypass Through User-Controlled Key in unshiftio/url-parse — unshiftio/url-parse 9.1 -2022-02-14
CVE-2021-25096 IP2Location Country Blocker < 2.26.5 - Ban Bypass — IP2Location Country Blocker 6.5 -2022-02-07
CVE-2022-0266 Authorization Bypass Through User-Controlled Key in livehelperchat/livehelperchat — livehelperchat/livehelperchat 6.8 -2022-01-19
CVE-2021-3852 Authorization Bypass Through User-Controlled Key in weseek/growi — weseek/growi 8.1 -2022-01-12
CVE-2021-44160 Carinal Tien Hospital Health Report System - Authorization Bypass Through User-Controlled Key — Health Report System 7.3 High2021-12-29
CVE-2021-24739 Logo Carousel < 3.4.2 - Unauthorised Private Post Access — Logo Carousel – Logo Slider, Logo Showcase, and Clients Logo Gallery 8.1 -2021-12-21
CVE-2021-43820 Permissions check bypass in Seafile — seafile-server 7.4 High2021-12-14
CVE-2021-3964 Authorization Bypass Through User-Controlled Key in elgg/elgg — elgg/elgg 8.1 -2021-12-01
CVE-2021-36329 Dell Emc Streaming Data Platform 安全漏洞 — Dell EMC Streaming Data Platform 6.5 Medium2021-11-30
CVE-2021-24892 Advanced Forms < 1.6.9 - Subscriber+ Arbitrary User Email Address Update via IDOR — Advanced Forms Ppro 8.8 -2021-11-23
CVE-2021-22967 PortlandLabs Concrete CMS 安全漏洞 — https://github.com/concrete5/concrete5 7.5 -2021-11-19
CVE-2021-22951 PortlandLabs Concrete CMS 安全漏洞 — https://github.com/concrete5/concrete5 7.5 -2021-11-19
CVE-2021-24840 Squaretype Modern Blog < 3.0.4 - Unauthenticated Private/Schedule Posts Disclosure — Squaretype 5.3 -2021-11-08
CVE-2021-39225 Missing permission check on Deck API — security-advisories 8.1 High2021-10-25
CVE-2021-40355 Teamcenter 代码问题漏洞 — Teamcenter V12.4 8.8 -2021-09-14
CVE-2021-37184 Siemens Industrial Edge Management 授权问题漏洞 — Industrial Edge Management 9.1 -2021-09-14
CVE-2021-37628 File Drop can be bypassed using Richdocuments app in nextcloud — security-advisories 7.5 High2021-09-07
CVE-2021-37630 Secret Circle can be joined without approval in Nextcloud Circles — security-advisories 6.5 Medium2021-09-07
CVE-2021-37631 Circle can be accessed by non-Circle members in Nextcloud Deck — security-advisories 6.5 Medium2021-09-07
CVE-2021-24562 LifterLMS < 4.21.2 - Access Other Student Grades/Answers via IDOR — LMS by LifterLMS – Online Course, Membership & Learning Management System Plugin for WordPress 7.5 -2021-08-23

Vulnerabilities classified as CWE-639 (通过用户控制密钥绕过授权机制) represent 1073 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.