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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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-2024-2577 SourceCodester Employee Task Management System update-employee.php authorization — Employee Task Management System 7.3 High2024-03-18
CVE-2024-2576 SourceCodester Employee Task Management System update-admin.php authorization — Employee Task Management System 7.3 High2024-03-18
CVE-2024-2575 SourceCodester Employee Task Management System task-details.php authorization — Employee Task Management System 7.3 High2024-03-18
CVE-2024-2574 SourceCodester Employee Task Management System edit-task.php authorization — Employee Task Management System 7.3 High2024-03-18
CVE-2023-36483 MAS (a Carrier brand) MASmobile Classic Authorization Bypass — MASmobile Classic 6.5 Medium2024-03-16
CVE-2023-6969 User Shortcodes Plus <= 2.0.2 - Insecure Direct Object Reference to Authenticated (Contributor+) Sensitive Information Disclosure via user_meta Shortcode — User Shortcodes Plus 4.3 Medium2024-03-13
CVE-2024-1640 Contact Form Builder Plugin: Multi Step Contact Form, Payment Form, Custom Contact Form Plugin by Bit Form <= 2.10.1 - Unauthenticated Insecure Direct Object Reference to Form Submission Alteration — Bit Form – Custom Contact Form, Multi Step, Conversational Form & Payment Form builder 5.3 Medium2024-03-13
CVE-2024-0839 FeedWordPress <= 2022.0222 - Insecure Direct Object Referece — FeedWordPress 5.3 Medium2024-03-13
CVE-2024-23112 Fortinet FortiOS 和 FortiProxy 安全漏洞 — FortiOS 7.2 High2024-03-12
CVE-2024-27302 Authorization Bypass Through User-Controlled Key in go-zero — go-zero 9.1 Critical2024-03-06
CVE-2024-1470 Elevation of Privilege attack on NetIQ Client login extension — NetIQ Client Login Extension 7.1 High2024-02-20
CVE-2024-25983 Msa-24-0006: idor on dashboard comments block 3.5 Low2024-02-19
CVE-2024-22455 Dell E-Lab Navigator 安全漏洞 — Mobility - E-Lab Navigator 4.4 Medium2024-02-14
CVE-2023-6724 IDOR in Simgesel Software's Hearing Tracking System (Barosel) — Hearing Tracking System 8.8 High2024-02-09
CVE-2023-6515 IDOR in Mia Technology's Mia-Med — MİA-MED 8.8 High2024-02-08
CVE-2024-1075 Minimal Coming Soon – Coming Soon Page <= 2.37 - Unauthenticated Maintenance Mode Bypass — Minimal Coming Soon – Coming Soon Page 3.7 Low2024-02-05
CVE-2023-6983 Display custom fields in the frontend – Post and User Profile Fields <= 1.2.1 - Insecure Direct Object Reference to Authenticated (Contributor+) Post Meta Disclosure — Display custom fields in the frontend – Post and User Profile Fields 4.3 Medium2024-02-05
CVE-2024-22305 WordPress Contact Form builder with drag & drop - Kali Forms Plugin <= 2.3.36 is vulnerable to Insecure Direct Object References (IDOR) — Contact Form builder with drag & drop for WordPress – Kali Forms 7.5 High2024-01-31
CVE-2024-0580 Omission of key-controlled authorization in Qsige — Sinergia, Sinergia 2.0, and Sinergia Corporativo 6.5 Medium2024-01-18
CVE-2023-6504 Profile Builder <= 3.10.7 - Insecure Direct Object Reference to Sensitive Information Exposure via user_meta Shortcode — User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor 4.3 Medium2024-01-11
CVE-2023-6875 POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress <= 2.8.7 - Authorization Bypass via type connect-app API — Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App 9.8 Critical2024-01-11
CVE-2023-6506 WP 2FA <= 2.5.0 - Insecure Direct Object Reference to Arbitrary Email Sending — WP 2FA – Two-factor authentication for WordPress 4.3 Medium2024-01-11
CVE-2023-6223 LearnPress <= 4.2.5.7 - Insecure Direct Object Reference to Information Disclosure — LearnPress – WordPress LMS Plugin for Create and Sell Online Courses 4.3 Medium2024-01-11
CVE-2023-48783 Fortinet PortiPortal 安全漏洞 — FortiPortal 4.9 Medium2024-01-10
CVE-2023-49251 Siemens SIMATIC CN 4100 安全漏洞 — SIMATIC CN 4100 8.8 High2024-01-09
CVE-2024-0264 SourceCodester Clinic Queuing System LoginRegistration.php authorization — Clinic Queuing System 7.3 High2024-01-07
CVE-2023-51502 WordPress WooCommerce Stripe Payment Gateway Plugin <= 7.6.1 is vulnerable to Insecure Direct Object References (IDOR) — WooCommerce Stripe Payment Gateway 7.5 High2024-01-05
CVE-2023-51503 WordPress WooCommerce Payments Plugin <= 6.6.2 is vulnerable to Insecure Direct Object References (IDOR) — WooPayments – Fully Integrated Solution Built and Supported by Woo 5.9 Medium2023-12-31
CVE-2023-46646 GitHub Enterprise Server 安全漏洞 — Enterprise Server 5.3 Medium2023-12-21
CVE-2023-49765 WordPress Rate my Post – WP Rating System Plugin <= 3.4.1 is vulnerable to Insecure Direct Object References (IDOR) — Rate my Post – WP Rating System 4.3 Medium2023-12-21

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