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-16121 nextlevelbuilder GoClaw exec_approval.go isSafeBin improper authorization — GoClaw 6.3 Medium 2026-07-18
CVE-2024-58367 SurrealDB before 2.0.4 Improper Authorization via SELECT Permissions — surrealdb 7.1 High 2026-07-18
CVE-2026-49977 tarteaucitron.js: data-cookie attribute can be used to delete arbitrary cookies — tarteaucitron.js 4.3 Medium 2026-07-17
CVE-2026-61718 bunkerweb: Read-only Web UI users can delete job cache files due to missing authorization on /cache/ routes — bunkerweb 5.4 Medium 2026-07-16
CVE-2026-45337 Better Auth: Device authorization approve and deny accept any authenticated session while the user code is pending — better-auth 7.6 High 2026-07-15
CVE-2026-49997 SurrealDB: Edge PERMISSIONS FOR delete bypassed when a connected node is deleted — surrealdb 5.4 Medium 2026-07-15
CVE-2026-58540 Windows Installer Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High 2026-07-14
CVE-2026-58277 Microsoft SharePoint Elevation of Privilege Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High 2026-07-14
CVE-2026-54121 Active Directory Certificate Services Elevation of Privilege Vulnerability — Windows 10 Version 1607 8.8 High 2026-07-14
CVE-2026-50344 Windows OLE Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High 2026-07-14
CVE-2026-50346 Netlogon RPC Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High 2026-07-14
CVE-2026-58631 Windows Admin Center (WAC) Remote Code Execution Vulnerability — Windows Admin Center 7.8 High 2026-07-14
CVE-2026-15594 waooAI waoowaoo Media hash.ts stablePublicIdFromStorageKey improper authorization — waoowaoo 3.7 Low 2026-07-13
CVE-2026-15510 Leantime API saveSetting improper authorization — Leantime 6.3 Medium 2026-07-12
CVE-2026-15509 Leantime JSON-RPC Endpoint addUser improper authorization — Leantime 6.3 Medium 2026-07-12
CVE-2026-56313 Capgo - Cross-Organization Account Disruption via SSO Prelink Endpoint — Capgo 8.1 High 2026-07-12
CVE-2026-56241 Capgo - RBAC Demotion Privilege Retention via Stale org_users.user_right — Capgo 8.3 High 2026-07-12
CVE-2026-15499 AstrBotDevs AstrBot Scheduled Task cron_tools.py FutureTaskTool.call improper authorization — AstrBot 6.3 Medium 2026-07-12
CVE-2026-15474 Eleveo Call Recording Software audio.jsp improper authorization — Call Recording Software 4.3 Medium 2026-07-12
CVE-2026-15473 Eleveo Call Recording Software Recorded Calls restoreCallAction.do improper authorization — Call Recording Software 6.3 Medium 2026-07-12
CVE-2026-15472 Eleveo Call Recording Software composeEmailAction.do improper authorization — Call Recording Software 4.3 Medium 2026-07-12
CVE-2026-15471 Eleveo Call Recording Software pci_dss_status.jsp improper authorization — Call Recording Software 4.3 Medium 2026-07-12
CVE-2026-15470 Eleveo Call Recording Software group.jsp improper authorization — Call Recording Software 4.3 Medium 2026-07-11
CVE-2026-56240 Capgo - Billing Authorization Bypass via Exhausted Usage Credits — Capgo 4.3 Medium 2026-07-11
CVE-2026-15377 Eleveo Call Recording Software sendlogfile improper authorization — Call Recording Software 4.3 Medium 2026-07-10
CVE-2026-15376 Eleveo Call Recording Software statisticReportAction.do improper authorization — Call Recording Software 6.3 Medium 2026-07-10
CVE-2026-15375 Eleveo Call Recording Software LDAP User users_ldap.jsp improper authorization — Call Recording Software 4.3 Medium 2026-07-10
CVE-2026-15374 Eleveo Call Recording Software Group roleAddAction.do improper authorization — Call Recording Software 6.3 Medium 2026-07-10
CVE-2026-15373 Eleveo Call Recording Software userAddAction.do improper authorization — Call Recording Software 6.3 Medium 2026-07-10
CVE-2026-55212 Pimcore: Insufficient Permission Check on Class Definition Creation Endpoint Allows Privilege Escalation — pimcore 7.1 High 2026-07-09

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