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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

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

986 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)
ConfidentialityRead 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.
IntegrityModify 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 ControlGain 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 DesignDivide 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 DesignEnsure 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 DesignUse 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 DesignFor 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, InstallationUse 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 IDTitleCVSSSeverityPublished
CVE-2026-2109 jsbroks COCO Annotator Delete Category undo improper authorization — COCO Annotator 5.4 Medium2026-02-07
CVE-2026-2107 yeqifu warehouse Log Info LoginfoController.java batchDeleteLoginfo improper authorization — warehouse 6.3 Medium2026-02-07
CVE-2026-2106 yeqifu warehouse Notice Management NoticeController.java batchDeleteNotice improper authorization — warehouse 6.3 Medium2026-02-07
CVE-2026-2105 yeqifu warehouse Department Management DeptController.java deleteDept improper authorization — warehouse 6.3 Medium2026-02-07
CVE-2026-2079 yeqifu warehouse Menu Management MenuController.java deleteMenu improper authorization — warehouse 6.3 Medium2026-02-07
CVE-2026-2078 yeqifu warehouse Permission Management PermissionController.java deletePermission improper authorization — warehouse 6.3 Medium2026-02-07
CVE-2026-2077 yeqifu warehouse Role Management RoleController.java deleteRole improper authorization — warehouse 6.3 Medium2026-02-07
CVE-2026-2076 yeqifu warehouse User Management Endpoint UserController.java deleteUser improper authorization — warehouse 6.3 Medium2026-02-07
CVE-2026-2015 Portabilis i-Educar Final Status Import FinalStatusImportService.php improper authorization — i-Educar 6.3 Medium2026-02-06
CVE-2026-2010 Sanluan PublicCMS Trade Payment TradePaymentService.java paid improper authorization — PublicCMS 4.2 Medium2026-02-06
CVE-2026-23623 Collabora Online vulnerable to Authorization Bypass — online 5.3 Medium2026-02-05
CVE-2026-1894 WeKan REST API checklistItems.js Checklist REST Bleed improper authorization — WeKan 6.3 Medium2026-02-04
CVE-2026-1892 WeKan REST API boards.js setBoardOrgs improper authorization — WeKan 5.0 Medium2026-02-04
CVE-2026-1733 Zhong Bang CRMEB :uni tidyOrder improper authorization — CRMEB 4.3 Medium2026-02-01
CVE-2026-1702 SourceCodester Pet Grooming Management Software User Management user.php improper authorization — Pet Grooming Management Software 6.3 Medium2026-01-30
CVE-2026-1597 Bdtask SalesERP Administrative Endpoint improper authorization — SalesERP 6.3 Medium2026-01-29
CVE-2026-1550 PHPGurukul Hospital Management System Admin Dashboard adminviews.py improper authorization — Hospital Management System 6.3 Medium2026-01-28
CVE-2026-24835 Podman Desktop Extension System Vulnerable to Authentication Bypass — podman-desktop 9.8AICriticalAI2026-01-28
CVE-2025-59100 Unauthenticated Access to the SQLite Database in dormakaba access manager — Access Manager 92xx-k5 9.8AICriticalAI2026-01-26
CVE-2026-24305 Azure Entra ID Elevation of Privilege Vulnerability — Microsoft Entra 9.3 Critical2026-01-22
CVE-2026-22022 Apache Solr: Unauthorized bypass of certain "predefined permission" rules in the RuleBasedAuthorizationPlugin — Apache Solr 9.8AICriticalAI2026-01-21
CVE-2025-14348 weMail <= 2.0.7 - Insufficient Authorization via x-wemail-user Header to Sensitive Information Disclosure — weMail: Email Marketing, Email Automation, Newsletters, Subscribers & Email Optins for WooCommerce 5.3 Medium2026-01-20
CVE-2026-1193 MineAdmin View view improper authorization — MineAdmin 6.3 Medium2026-01-19
CVE-2026-1141 PHPGurukul News Portal Add Sub-Admin add-subadmins.php improper authorization — News Portal 6.3 Medium2026-01-19
CVE-2026-1112 Sanluan PublicCMS Trade Address Deletion Endpoint TradeAddressController.java delete improper authorization — PublicCMS 5.4 Medium2026-01-18
CVE-2026-1106 Chamilo LMS Legal Consent SocialController.php deleteLegal improper authorization — LMS 5.4 Medium2026-01-18
CVE-2026-20960 PowerApps Desktop Client Remote Code Execution Vulnerability — Microsoft Power Apps Desktop Client 8.0 High2026-01-16
CVE-2026-22252 LibreChat MCP Stdio Remote Command Execution — LibreChat 9.1 Critical2026-01-12
CVE-2025-67603 Lack of client authorization allows arbitrary users to influence the firewall configuration — Foomuuri 5.3 -2026-01-08
CVE-2026-22042 RustFS has IAM Incorrect Authorization in ImportIam that Allows Privilege Escalation — rustfs 8.8 -2026-01-08

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