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

Goal: 1000 CNY · Raised: 1020 CNY

100%

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

1123 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-2025-12997 Medtronic CareLink Network 安全漏洞 — CareLink Network 2.2 Low2025-12-04
CVE-2025-13109 HUSKY – Products Filter Professional for WooCommerce <= 1.3.7.2 - Authenticated (Subscriber+) Insecure Direct Object Reference via 'woof_add_query/woof_remove_query' — HUSKY – Products Filter Professional for WooCommerce 4.3 Medium2025-12-03
CVE-2025-41086 Authorization bypass in GAMS from GAMS Development Corp. — GAMS 8.1AIHighAI2025-12-02
CVE-2025-66306 Grav vulnerable to Information Disclosure via IDOR in Grav Admin Panel — grav 4.3 Medium2025-12-01
CVE-2025-13615 StreamTube Core <= 4.78 - Unauthenticated Arbitrary User Password Change — StreamTube Core 9.8 Critical2025-11-30
CVE-2025-13768 Uniong|WebITR - Authorization Bypass — WebITR 7.5 High2025-11-28
CVE-2025-13157 QODE Wishlist for WooCommerce <= 1.2.7 - Unauthenticated Insecure Direct Object Reference to Wishlist Update — QODE Wishlist for WooCommerce 5.3 Medium2025-11-27
CVE-2025-13382 Frontend File Manager Plugin <= 23.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary File Renaming — Frontend File Manager Plugin 4.3 Medium2025-11-25
CVE-2025-13389 Admin and Customer Messages After Order for WooCommerce: OrderConvo <= 14 - Missing Authorization to Unauthenticated Information Disclosure — Admin and Customer Messages After Order for WooCommerce: OrderConvo 5.3 Medium2025-11-25
CVE-2025-12040 Wishlist for WooCommerce <= 1.1.3 - Insecure Direct Object Reference to Unauthenticated Wishlist Manipulation — Wishlist for WooCommerce 6.5 Medium2025-11-25
CVE-2025-13452 Admin and Customer Messages After Order for WooCommerce: OrderConvo <= 14 - Missing Authorization to Unauthenticated User Impersonation in Order Messages — Admin and Customer Messages After Order for WooCommerce: OrderConvo 4.3 Medium2025-11-25
CVE-2025-10039 ELEX WordPress HelpDesk & Customer Ticketing System <= 3.2.9 - Authenticated (Subscriber+) Insecure Direct Object Reference via 'eh_crm_ticket_single_view_client' — ELEX WordPress HelpDesk & Customer Ticketing System 4.3 Medium2025-11-21
CVE-2025-12881 Return Refund and Exchange For WooCommerce <= 4.5.5 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Order Message Read — Return Refund and Exchange For WooCommerce 5.4 Medium2025-11-21
CVE-2025-12086 Return Refund and Exchange For WooCommerce <= 4.5.5 - Insecure Direct Object Reference to Authenticated (Subscriber+) Refund Request Cancellation — Return Refund and Exchange For WooCommerce 4.3 Medium2025-11-21
CVE-2025-65034 Rallly Improper Authorization Allows Reopening of Any Finalized Poll via Public pollId — rallly 8.1 High2025-11-19
CVE-2025-65032 Rallly Has an IDOR Vulnerability in Participant Rename Function Allows Unauthorized Modification of Other Users’ Names — rallly 6.5 Medium2025-11-19
CVE-2025-12766 Insecure Direct Object Reference (IDOR) vulnerability in the Management Console of affected versions of BlackBerry AtHoc. — BlackBerry® AtHoc® (OnPrem) 5.0 Medium2025-11-19
CVE-2025-12427 YITH WooCommerce Wishlist <= 4.10.0 - Unauthenticated Insecure Direct Object Reference to Unauthenticated Wishlist Rename — YITH WooCommerce Wishlist 5.3 Medium2025-11-19
CVE-2025-12524 Post Type Switcher <= 4.0.0 - Insecure Direct Object Reference to Authenticated (Author+) Post Type Change — Post Type Switcher 5.4 Medium2025-11-18
CVE-2025-8855 2FA Expiry Bypass in Optimus Software's Brokerage Automation — Brokerage Automation 8.1 High2025-11-14
CVE-2025-64706 Typebot IDOR Vulnerability: Unauthorized API Token Deletion and Exposure — typebot.io 5.0 Medium2025-11-13
CVE-2025-41069 Insecure Direct Object References (IDOR) in DeporSite of T-Innova DeporSite — DSuite 2025 8.1 -2025-11-13
CVE-2025-12366 Page Builder: Pagelayer – Drag and Drop website builder <= 2.0.5 - Authenticated (Author+) Insecure Direct Object Reference — Page Builder: Pagelayer – Drag and Drop website builder 4.3 Medium2025-11-13
CVE-2025-12903 Payment Plugins Braintree For WooCommerce <= 3.2.78 - Missing Authorization to Payment Token Exposure and Transaction Fraud — Payment Plugins Braintree For WooCommerce 7.5 High2025-11-12
CVE-2025-12833 GeoDirectory – WP Business Directory Plugin and Classified Listings Directory <= 2.8.139 - Missing Authorization to Authenticated (Author+) Arbitrary Image Attachment — GeoDirectory – WP Business Directory Plugin and Classified Listings Directory 4.3 Medium2025-11-12
CVE-2025-12087 Wishlist and Save for later for Woocommerce <= 1.1.22 - Insecure Direct Object Reference to Authenticated (Subscriber+) Wishlist Item Deletion — Wishlist and Save for later for Woocommerce 4.3 Medium2025-11-12
CVE-2025-12126 The Total Book Project <= 1.0 - Insecure Direct Object Reference to Authenticated (Contributor+) Book Manipulation — The Total Book Project 5.4 Medium2025-11-11
CVE-2025-11532 Wisly <= 1.0.0 - Insecure Direct Object Reference to Unauthenticated Wishlist Manipulation — Wisly 5.3 Medium2025-11-11
CVE-2025-11748 Groups <= 3.7.0 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Group Join — Groups 4.3 Medium2025-11-08
CVE-2025-12353 WPFunnels <= 3.6.2 - Unauthorized User Registration — WPFunnels – Funnel Builder for WooCommerce with Checkout & One Click Upsell 5.3 Medium2025-11-08

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