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-4686 Authorization Bypass Through User-Controlled Key in usememos/memos — usememos/memos 9.1 -2022-12-23
CVE-2022-3794 Jeg Elementor Kit <= 2.5.6 - Authorization Bypass — Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress 5.4 Medium2022-12-22
CVE-2022-3805 Jeg Elementor Kit <= 2.5.6 - Unauthenticated Authorization Bypass — Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress 8.6 High2022-12-22
CVE-2022-4505 Authorization Bypass Through User-Controlled Key in openemr/openemr — openemr/openemr 8.8 High2022-12-15
CVE-2022-2808 IDOR in Prens Student Information System — Prens Student Information System 8.8 High2022-12-12
CVE-2022-3995 TeraWallet – For WooCommerce <= 1.4.3 - Insecure Direct Object Reference — Wallet for WooCommerce 4.3 Medium2022-11-29
CVE-2022-3589 Miele: Vulnerability in cloud service used by appWash — appWash 8.1 High2022-11-21
CVE-2022-3282 Drag and Drop Multiple File Upload < 1.3.6.5 - File Upload Size Limit Bypass — Drag and Drop Multiple File Upload – Contact Form 7 8.1 -2022-10-17
CVE-2022-1613 Restricted Site Access < 7.3.2 - Access Bypass via IP Spoofing — Restricted Site Access 5.3 -2022-09-26
CVE-2022-1580 Site Offline < 1.5.3 - Access Bypass — Site Offline Or Coming Soon Or Maintenance Mode 4.3 -2022-09-19
CVE-2022-2913 Login No Captcha reCAPTCHA < 1.7 - IP Check Bypass — Login No Captcha reCAPTCHA 4.3 -2022-09-16
CVE-2022-2877 Titan Anti-spam & Security < 7.3.1 - Protection Bypass due to IP Spoofing — Titan Anti-spam & Security 5.3 -2022-09-16
CVE-2022-2080 Sensei LMS < 4.5.2 - Arbitrary Private Message Sending via IDOR — Sensei LMS – Online Courses, Quizzes, & Learning 5.4 -2022-08-29
CVE-2021-4142 Red Hat Satellite 授权问题漏洞 — candlepin 5.7 -2022-08-24
CVE-2022-2312 Student Result or Employee Database < 1.7.5 - Stored Cross Site Scripting via CSRF — Student Result or Employee Database 5.4 -2022-08-22
CVE-2022-2198 WPQA < 5.7 - Subscriber+ Private Message Disclosure via IDOR — WPQA Builder 4.3 -2022-08-22
CVE-2022-2824 Authorization Bypass Through User-Controlled Key in openemr/openemr — openemr/openemr 8.8 High2022-08-15
CVE-2022-2535 SearchWP Live Ajax Search < 1.6.2 - Unauthenticated Arbitrary Post Title Disclosure — SearchWP Live Ajax Search 5.3 -2022-08-15
CVE-2022-2730 Authorization Bypass Through User-Controlled Key in openemr/openemr — openemr/openemr 8.2 -2022-08-09
CVE-2022-2367 WSM Downloader <= 1.4.0 - Domain Name Restriction Bypass — WSM Downloader 7.5 -2022-08-08
CVE-2022-1600 YOP Poll < 6.4.3 - IP Spoofing — YOP Poll 5.3 -2022-08-01
CVE-2022-33944 ICSA-22-200-01 MiCODUS MV720 GPS tracker Authorization Bypass Through User-Controlled Key — MV720 6.5 Medium2022-07-20
CVE-2022-34150 ICSA-22-200-01 MiCODUS MV720 GPS tracker Authorization Bypass Through User-Controlled Key — MV720 7.1 High2022-07-20
CVE-2021-24655 WP User Manager < 2.6.3 - Arbitrary User Password Reset to Account Compromise — WP User Manager – User Profile Builder & Membership 7.5 -2022-07-17
CVE-2022-0624 Authorization Bypass Through User-Controlled Key in ionicabizau/parse-path — ionicabizau/parse-path 7.3 -2022-06-28
CVE-2022-1614 WP-Email < 2.69.0 - Anti-Spam Protection Bypass via IP Spoofing — WP-EMail 7.5 -2022-06-20
CVE-2022-31027 Authorization Bypass Through User-Controlled Key when using CILogonOAuthenticator in oauthenticator — oauthenticator 4.2 Medium2022-06-06
CVE-2022-1996 Authorization Bypass Through User-Controlled Key in emicklei/go-restful — emicklei/go-restful 9.1 -2022-06-06
CVE-2022-1810 Authorization Bypass Through User-Controlled Key in publify/publify — publify/publify 7.1 -2022-05-23
CVE-2022-29159 Possibility for anyone to add a stack with existing tasks on anyone's board in Nextcloud Deck — security-advisories 5.0 Medium2022-05-20

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