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-2023-47191 WordPress Youzify Plugin <= 1.2.2 is vulnerable to Insecure Direct Object References (IDOR) — Youzify – BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress 6.5 Medium2023-12-21
CVE-2023-32799 WordPress WooCommerce Ship to Multiple Addresses Plugin <= 3.8.3 is vulnerable to Insecure Direct Object References (IDOR) — Shipping Multiple Addresses 6.5 Medium2023-12-21
CVE-2023-32747 WordPress WooCommerce Bookings Plugin <= 1.15.78 is vulnerable to Insecure Direct Object References (IDOR) — WooCommerce Bookings 5.4 Medium2023-12-21
CVE-2023-35914 WordPress WooCommerce Subscriptions Plugin <= 5.1.2 is vulnerable to Insecure Direct Object References (IDOR) — Woo Subscriptions 7.5 High2023-12-20
CVE-2023-35916 WordPress WooCommerce Payments Plugin <= 5.9.0 is vulnerable to Insecure Direct Object References (IDOR) — WooPayments – Fully Integrated Solution Built and Supported by Woo 7.5 High2023-12-20
CVE-2023-35876 WordPress WooCommerce Square Plugin <= 3.8.1 is vulnerable to Insecure Direct Object References (IDOR) — WooCommerce Square 8.1 High2023-12-20
CVE-2023-36520 WordPress Editorial Calendar Plugin <= 3.7.12 is vulnerable to Insecure Direct Object References (IDOR) — Editorial Calendar 5.4 Medium2023-12-20
CVE-2023-37871 WordPress WooCommerce GoCardless Gateway Plugin <= 2.5.6 is vulnerable to Insecure Direct Object References (IDOR) — GoCardless 8.2 High2023-12-20
CVE-2023-38513 WordPress Photo Engine Plugin <= 6.2.5 is vulnerable to Insecure Direct Object References (IDOR) — Photo Engine (Media Organizer & Lightroom) 5.4 Medium2023-12-20
CVE-2023-41796 WordPress Sunshine Photo Cart Plugin < 3.0.0 is vulnerable to Insecure Direct Object References (IDOR) — Sunshine Photo Cart: Free Client Galleries for Photographers 5.3 Medium2023-12-20
CVE-2023-46311 WordPress wpDiscuz Plugin <= 7.6.3 is vulnerable to Insecure Direct Object References (IDOR) — Comments – wpDiscuz 2.7 Low2023-12-20
CVE-2023-6929 Authorization Bypass Through User-Controlled Key in EuroTel ETL3100 — ETL3100 7.5 High2023-12-19
CVE-2022-43450 WordPress Stream Plugin <= 3.9.2 is vulnerable to Insecure Direct Object References (IDOR) — Stream 4.3 Medium2023-12-19
CVE-2023-49812 WordPress WP Photo Album Plus Plugin <= 8.5.02.005 is vulnerable to Insecure Direct Object References (IDOR) — WP Photo Album Plus 5.3 Medium2023-12-19
CVE-2023-6341 Catalis CM360 allows authentication bypass — CMS360 5.3 Medium2023-11-30
CVE-2023-6226 WP Shortcodes Plugin — Shortcodes Ultimate <= 5.13.3 - Insecure Direct Object Reference to Information Disclosure — WP Shortcodes Plugin — Shortcodes Ultimate 4.3 Medium2023-11-28
CVE-2023-48304 Nextcloud Server vulnerable to attacker enabling/disabling birthday calendar for any user — security-advisories 4.3 Medium2023-11-21
CVE-2023-6144 Dev Blog v1.0 - ATO — Dev Blog 9.1 Critical2023-11-20
CVE-2023-3869 wpDiscuz <= 7.6.3 - Insecure Direct Object Reference to Comment Rating Increase/Decrease — Comments – wpDiscuz 5.3 Medium2023-10-20
CVE-2023-3998 wpDiscuz <= 7.6.3 - Insecure Direct Object Reference to Post Rating Increase/Decrease — Comments – wpDiscuz 5.3 Medium2023-10-20
CVE-2023-43668 Apache InLong: Jdbc Connection Security Bypass in InLong — Apache InLong 9.8 -2023-10-16
CVE-2023-44981 Apache ZooKeeper: Authorization bypass in SASL Quorum Peer Authentication — Apache ZooKeeper 9.1 -2023-10-11
CVE-2023-44249 Fortinet FortiManager 安全漏洞 — FortiManager 4.1 Medium2023-10-10
CVE-2023-42455 Wazuh vulnerable to user privilege escalation — wazuh-kibana-app 8.8 High2023-10-09
CVE-2023-2544 Authorization Bypass on UPV PEIX — UPV PEIX 5.3 Medium2023-10-03
CVE-2023-32669 Authorization Bypass on BuddyBoss — BuddyBoss 5.4 Medium2023-10-03
CVE-2023-4101 Multiple vulnerabilities in IDM Sistemas QSige — QSige 8.8 High2023-10-03
CVE-2023-4099 Multiple vulnerabilities in IDM Sistemas QSige — QSige 7.6 High2023-10-03
CVE-2023-44206 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 15 9.1 -2023-09-27
CVE-2023-44205 Acronis Cyber Protect 安全漏洞 — Acronis Cyber Protect 15 7.5 -2023-09-27

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