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-2025-29827 Azure Automation Elevation of Privilege Vulnerability — Azure Automation 9.9 Critical2025-05-08
CVE-2025-4104 Frontend Dashboard 1.0 - 2.2.6 - Missing Authorization to Unauthenticated Privilege Escalation via fed_wp_ajax_fed_login_form_post Function — Frontend Dashboard 9.8 Critical2025-05-07
CVE-2025-3921 PeproDev Ultimate Profile Solutions 1.9.1 - 7.5.2 - Missing Authorization to Limited Unauthenticated Arbitrary User Meta Update via handel_ajax_req Function — PeproDev Ultimate Profile Solutions 8.2 High2025-05-07
CVE-2025-3924 PeproDev Ultimate Profile Solutions 1.9.1 - 7.5.2 - Missing Authorization to Unauthenticated Email Enumeration — PeproDev Ultimate Profile Solutions 5.3 Medium2025-05-07
CVE-2025-3918 Job Listings 0.1 - 0.1.1 - Unauthenticated Privilege Escalation via register_action Function — Job Listings 9.8 Critical2025-05-03
CVE-2025-4136 Weitong Mall Sale Endpoint improper authorization — Mall 5.4 Medium2025-04-30
CVE-2025-30392 Azure AI Bot Elevation of Privilege Vulnerability — Azure AI Bot Service 9.8 Critical2025-04-30
CVE-2025-30390 Azure ML Compute Elevation of Privilege Vulnerability — Azure Machine Learning 9.9 Critical2025-04-30
CVE-2025-30389 Azure Bot Framework SDK Elevation of Privilege Vulnerability — Azure AI Bot Service 8.7 High2025-04-30
CVE-2025-32972 The lesscss script service allows cache clearing without programming right — xwiki-platform 2.7 Low2025-04-30
CVE-2025-4017 20120630 Novel-Plus LogController.java list improper authorization — Novel-Plus 4.3 Medium2025-04-28
CVE-2025-4016 20120630 Novel-Plus LogController.java deleteIndex improper authorization — Novel-Plus 5.4 Medium2025-04-28
CVE-2025-3981 wowjoy 浙江湖州华卓信息科技有限公司 Internet Doctor Workstation System details improper authorization — Internet Doctor Workstation System 4.3 Medium2025-04-27
CVE-2025-3980 wowjoy 浙江湖州华卓信息科技有限公司 Internet Doctor Workstation System list improper authorization — Internet Doctor Workstation System 4.3 Medium2025-04-27
CVE-2025-3977 iteachyou Dreamer CMS Attachment download improper authorization — Dreamer CMS 4.3 Medium2025-04-27
CVE-2025-3967 itwanger paicoding Article post improper authorization — paicoding 5.4 Medium2025-04-27
CVE-2025-2850 GL.iNet GL-A1300 Slate Plus Download Interface improper authorization — GL-A1300 Slate Plus 3.5 Low2025-04-26
CVE-2025-32964 ManageWiki vulnerable to permission bypass when disabling extensions requiring certain permissions in Special:ManageWiki/extensions — ManageWiki 4.6 Medium2025-04-22
CVE-2025-3587 ZeroWdd/code-projects studentmanager getTeacherList improper authorization — studentmanager 6.3 Medium2025-04-14
CVE-2025-3569 JamesZBL/code-projects db-hospital-drug ShiroConfig.java improper authorization — db-hospital-drug 6.3 Medium2025-04-14
CVE-2025-3567 veal98 小牛肉 Echo 开源社区系统 Ticket LoginTicketInterceptor.java preHandle improper authorization — Echo 开源社区系统 4.3 Medium2025-04-14
CVE-2025-3564 huanfenz/code-projects StudentManager Teacher String improper authorization — StudentManager 4.3 Medium2025-04-14
CVE-2025-3550 wowjoy 浙江湖州华卓信息科技有限公司 Internet Doctor Workstation System detail improper authorization — Internet Doctor Workstation System 4.3 Medium2025-04-14
CVE-2025-3537 Tutorials-Website Employee Management System update-user.php improper authorization — Employee Management System 5.3 Medium2025-04-13
CVE-2025-3536 Tutorials-Website Employee Management System delete-user.php improper authorization — Employee Management System 6.5 Medium2025-04-13
CVE-2025-29794 Microsoft SharePoint Remote Code Execution Vulnerability — Microsoft SharePoint Enterprise Server 2016 8.8 High2025-04-08
CVE-2025-30373 Graylog Authenticated HTTP inputs do ingest message even if Authorization header is missing or has wrong value — graylog2-server 6.5 Medium2025-04-07
CVE-2025-3202 ageerle ruoyi-ai SysNoticeController.java improper authorization — ruoyi-ai 7.3 High2025-04-04
CVE-2025-3199 ageerle ruoyi-ai API Interface SysModelController.java improper authorization — ruoyi-ai 7.3 High2025-04-04
CVE-2025-26683 Azure Playwright Elevation of Privilege Vulnerability — Azure Playwright 8.1 High2025-03-31

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