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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-285 (授权机制不恰当) — Vulnerability Class 1306

1306 vulnerabilities classified as CWE-285 (授权机制不恰当). AI Chinese analysis included.

CWE-285 represents a critical access control weakness where an application fails to verify whether a user possesses the necessary permissions to access a specific resource or execute a particular action. Attackers typically exploit this vulnerability by manipulating request parameters, such as changing user IDs in URLs or API calls, to bypass security checks and access data belonging to other users or perform administrative tasks. This often leads to severe data breaches or unauthorized system modifications. To prevent such flaws, developers must implement robust, centralized authorization mechanisms that consistently validate user privileges for every sensitive operation. Relying solely on client-side checks is insufficient; instead, server-side enforcement using role-based or attribute-based access control ensures that only authenticated and authorized entities can interact with protected resources, thereby maintaining strict integrity and confidentiality.

MITRE CWE Description
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Common Consequences (3)
Confidentiality Read Application Data, Read Files or Directories
An attacker could read sensitive data, either by reading the data directly from a data store that is not properly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
Integrity Modify Application Data, Modify Files or Directories
An attacker could modify sensitive data, either by writing the data directly to a data store that is not properly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access Control Gain Privileges or Assume Identity, Execute Unauthorized Code or Commands
When access control checks are not applied consistently - or not at all - an attacker could gain privileges and execute unauthorized code or commands by modifying or reading critical data directly, or by accessing insufficiently-protected, privileged functionality.
Mitigations (5)
Architecture and Design Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Architecture and Design Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to…
Architecture and Design Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Architecture and Design For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests …
System Configuration, Installation Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
Examples (2)
This function runs an arbitrary SQL query on a given database, returning the result of the query.
function runEmployeeQuery($dbName, $name){ mysql_select_db($dbName,$globalDbHandle) or die("Could not open Database".$dbName); //Use a prepared statement to avoid CWE-89 $preparedStatement = $globalDbHandle->prepare('SELECT * FROM employees WHERE name = :name'); $preparedStatement->execute(array(':name' => $name)); return $preparedStatement->fetchAll(); } /.../ $employeeRecord = runEmployeeQuery('EmployeeDB',$_GET['EmployeeName']);
Bad · PHP
The following program could be part of a bulletin board system that allows users to send private messages to each other. This program intends to authenticate the user before deciding whether a private message should be displayed. Assume that LookupMessageObject() ensures that the $id argument is numeric, constructs a filename based on that id, and reads the message details from that file. Also ass…
sub DisplayPrivateMessage { my($id) = @_; my $Message = LookupMessageObject($id); print "From: " . encodeHTML($Message->{from}) . "<br>\n"; print "Subject: " . encodeHTML($Message->{subject}) . "\n"; print "<hr>\n"; print "Body: " . encodeHTML($Message->{body}) . "\n"; } my $q = new CGI; # For purposes of this example, assume that CWE-309 and # CWE-523 do not apply. if (! AuthenticateUser($q->param('username'), $q->param('password'))) { ExitError("invalid username or password"); } my $id = $q->param('id'); DisplayPrivateMessage($id);
Bad · Perl
CVE ID Title CVSS Severity Published
CVE-2026-56231 Capgo - Broken Object Level Authorization in Build Job Control via jobId Parameter — Capgo 7.6 High 2026-06-24
CVE-2026-46552 NocoDB: Shared-base link access can invite arbitrary users as persistent base members — nocodb 5.8 Medium 2026-06-23
CVE-2026-56311 Capgo - Unauthenticated Cross-Tenant Disclosure via get_current_plan_max_org RPC — Capgo 5.3 Medium 2026-06-22
CVE-2026-12799 BerriAI litellm Incomplete Fix CVE-2025-0628 internal_user_endpoints.py ui_view_users improper authorization — litellm 4.3 Medium 2026-06-21
CVE-2026-12771 BerriAI litellm M2M JWT user_api_key_auth.py improper authorization — litellm 5.0 Medium 2026-06-21
CVE-2026-12770 BerriAI litellm Admin Key key_management_endpoints.py improper authorization — litellm 5.4 Medium 2026-06-21
CVE-2026-56295 Capgo - Policy Enforcement Bypass in Webhook Management Endpoints via Non-Expiring API Keys — Capgo 6.3 Medium 2026-06-20
CVE-2026-12673 Liquidfiles 授权问题漏洞 — liquidfiles - - 2026-06-20
CVE-2026-48089 DevGuard has improper authorization on public assets — devguard - - 2026-06-19
CVE-2026-49338 Subsonic API: any authenticated user can delete or read any other user's playlist (IDOR) — gonic 7.1 High 2026-06-19
CVE-2026-20190 Cisco Identity Services Engine Information Disclosure Vulnerability — Cisco Identity Services Engine Software 7.5 High 2026-06-17
CVE-2026-12213 hcengineering Huly Platform User Information operations.ts getAccountInfo improper authorization — Huly Platform 4.3 Medium 2026-06-15
CVE-2026-47342 Apache OFBiz: Privilege Escalation via updateOrRemove Authorization Bypass — Apache OFBiz - - 2026-06-10
CVE-2026-46668 SpiceDB: Caveat structures with nested lists can result in improper cache reuse — spicedb - - 2026-06-10
CVE-2026-47298 Microsoft SharePoint Server Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.0 High 2026-06-09
CVE-2026-45503 Microsoft Exchange Server Information Disclosure Vulnerability — Microsoft Exchange Server 2016 Cumulative Update 23 8.1 High 2026-06-09
CVE-2026-45490 .NET SDK Elevation of Privilege Vulnerability — .NET 10.0 7.8 High 2026-06-09
CVE-2026-42902 Microsoft PowerToys Elevation of Privilege Vulnerability — Microsoft PowerToys 7.8 High 2026-06-09
CVE-2026-11619 Dolibarr ERP CRM Legacy Filemanager config.inc.php improper authorization — ERP CRM 6.3 Medium 2026-06-09
CVE-2026-11533 imvks786 student_management_system Student Deletion Endpoint see.php improper authorization — student_management_system 5.4 Medium 2026-06-08
CVE-2026-46656 Bludit CMS has improper authorization and mediation failure leading to persistent ghost sessions — bludit 8.8 High 2026-06-08
CVE-2026-11521 Mohammed-eid35 bank-management-system-springboot Transaction Endpoint TransactionController.java improper authorization — bank-management-system-springboot 6.3 Medium 2026-06-08
CVE-2026-11519 SourceCodester Inventory System Account Creation users_handler.php improper authorization — Inventory System 6.3 Medium 2026-06-08
CVE-2026-11476 Kushan2k student-management-system Profile Update Endpoint AdminController.php edit-admin improper authorization — student-management-system 6.3 Medium 2026-06-08
CVE-2026-11462 Chengdu Everbrite Network Technology BeikeShop Stripe Plugin StripeController.php callback improper authorization — BeikeShop 7.3 High 2026-06-07
CVE-2026-11441 theonedev Pull Request issues canAccessIssue improper authorization — onedev 6.3 Medium 2026-06-06
CVE-2026-11440 theonedev REST API default-branch improper authorization — onedev 6.3 Medium 2026-06-06
CVE-2026-11439 theonedev Parent Project projects improper authorization — onedev 6.3 Medium 2026-06-06
CVE-2026-11438 theonedev projects improper authorization — onedev 6.3 Medium 2026-06-06
CVE-2026-10580 Hippoo Mobile App for WooCommerce <= 1.9.4 - Unauthenticated Authentication Bypass to Administrator Account Takeover via REST API — Hippoo Mobile App for WooCommerce 9.8 Critical 2026-06-05

Vulnerabilities classified as CWE-285 (授权机制不恰当) represent 1306 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.