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-11336 tittuvarghese CollegeManagementSystem Admin admin_page.php improper authorization — CollegeManagementSystem 6.3 Medium 2026-06-05
CVE-2026-10876 SourceCodester Ship Ferry Ticket Reservation System admin improper authorization — Ship Ferry Ticket Reservation System 6.3 Medium 2026-06-04
CVE-2026-48579 Microsoft Exchange Online Information Disclosure Vulnerability — Microsoft Exchange Online 9.1 Critical 2026-06-04
CVE-2026-41522 Iris has an Improper Authorization issue — iris-web - - 2026-06-04
CVE-2026-10693 SourceCodester Online Boat Reservation System Administrative Endpoint improper authorization — Online Boat Reservation System 6.3 Medium 2026-06-03
CVE-2026-33398 Authenticated users can read hidden forum posts through `/forum/get_quotes` — Nameless - - 2026-06-02
CVE-2026-41115 Apache Kafka: Improper Authorization in CONSUMER_GROUP_DESCRIBE API — Apache Kafka - - 2026-06-02
CVE-2026-10294 PackageKit API pk-transaction.c g_file_test improper authorization — PackageKit 4.3 Medium 2026-06-01
CVE-2026-10285 DevaslanPHP project-management Ticket KanbanScrumHelper.php recordUpdated improper authorization — project-management 5.4 Medium 2026-06-01
CVE-2026-10284 DevaslanPHP project-management Livewire ViewTicket.php doDeleteComment improper authorization — project-management 5.4 Medium 2026-06-01
CVE-2026-10282 Bottelet DaybydayCRM DocumentsController.php view improper authorization — DaybydayCRM 4.3 Medium 2026-06-01
CVE-2026-0072 Google Android 安全漏洞 — Android XR - - 2026-06-01
CVE-2026-45275 Nextcloud: Authorization bypass in approval feature allows unauthorized file sharing with approvers — security-advisories 6.5 Medium 2026-06-01
CVE-2026-10272 a4m4 Student-Management-System deleteform.php improper authorization — Student-Management-System 6.5 Medium 2026-06-01
CVE-2026-10269 decolua 9router HTTP Header dashboardGuard.js isAuthenticated improper authorization — 9router 6.3 Medium 2026-06-01
CVE-2026-40963 Apache Airflow: DAG authorization bypass on /ui/structure/structure_data — Apache Airflow - - 2026-06-01
CVE-2026-10236 SourceCodester Water Billing Management System User Management Endpoint Users.php save improper authorization — Water Billing Management System 7.3 High 2026-06-01
CVE-2026-46605 Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Incomplete authorization during destination removal — Apache ActiveMQ Broker - - 2026-06-01
CVE-2026-10218 nextlevelbuilder GoClaw evolution_handlers.go auth improper authorization — GoClaw 5.4 Medium 2026-06-01
CVE-2026-10215 Dolibarr ERP CRM Leave Request REST API api_holidays.class.php checkUserAccessToObject improper authorization — ERP CRM 4.3 Medium 2026-06-01
CVE-2026-48810 FreeScout: Thread Edit Authorization Bypass via Missing Mailbox Check — freescout 4.3 Medium 2026-05-29
CVE-2026-47740 Shopper: Authorization bypass in multiple Livewire admin components — shopper 8.1 High 2026-05-29
CVE-2026-10070 macrozheng mall Super Admin Password update improper authorization — mall 4.7 Medium 2026-05-29
CVE-2026-47713 AnythingLLM: Legacy mobile device tokens bypass multi-user workspace scoping after mode migration — anything-llm 2.0 Low 2026-05-28
CVE-2026-45297 Cross-tenant IDOR on feature-flag and assist-stats routes via {project_id} case mismatch — openreplay - - 2026-05-28
CVE-2026-47673 Hono: JWT middleware accepts any Authorization scheme, not only Bearer — hono 4.8 Medium 2026-05-28
CVE-2026-6938 IBM® Db2® is vulnerable to authorization bypass when uploading to a remote object storage path with a special query — Db2 6.5 Medium 2026-05-27
CVE-2026-46620 e107: CSRF in comment.php moderation endpoints via token-optional validation in session_handler::check() — e107 6.5 Medium 2026-05-26
CVE-2026-9484 SourceCodester Student Grades Management System classroom.php removeStudentFromClassroom improper authorization — Student Grades Management System 6.3 Medium 2026-05-25
CVE-2026-9483 SourceCodester Student Grades Management System grades.php improper authorization — Student Grades Management System 6.3 Medium 2026-05-25

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