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-12958 Rankology SEO and Analytics Tool <= 2.0 - Incorrect Authorization to Authenticated (Editor+) Header & Footer Code Creation — Rankology SEO and Analytics Tool 2.7 Low2026-01-07
CVE-2025-9294 Quiz And Survey Master <= 10.3.1 - Missing Authorization to Authenticated (Subscriber+) Quiz Results Deletion — Quiz and Survey Master (QSM) – Easy Quiz and Survey Maker 4.3 Medium2026-01-06
CVE-2025-61781 GraphQL IDOR allows authenticated user to delete workspace content of other users — opencti 7.1 High2026-01-05
CVE-2026-0574 yeqifu warehouse Request UserController.java saveUserRole improper authorization — warehouse 6.3 Medium2026-01-04
CVE-2025-15213 code-projects Student File Management System File Download download.php improper authorization — Student File Management System 4.3 Medium2025-12-30
CVE-2025-15126 JeecgBoot getPositionUserList improper authorization — JeecgBoot 3.1 Low2025-12-28
CVE-2025-15125 JeecgBoot queryDepartPermission improper authorization — JeecgBoot 3.1 Low2025-12-28
CVE-2025-15124 JeecgBoot list getParameterMap improper authorization — JeecgBoot 3.1 Low2025-12-28
CVE-2025-15123 JeecgBoot datarule improper authorization — JeecgBoot 3.1 Low2025-12-28
CVE-2025-15122 JeecgBoot datarule loadDatarule improper authorization — JeecgBoot 3.1 Low2025-12-28
CVE-2025-15120 JeecgBoot getDeptRoleList improper authorization — JeecgBoot 3.1 Low2025-12-28
CVE-2025-15119 JeecgBoot list queryPageList improper authorization — JeecgBoot 3.1 Low2025-12-28
CVE-2025-15118 macrozheng mall Member Endpoint update improper authorization — mall 4.3 Medium2025-12-28
CVE-2025-15106 getmaxun Authentication Endpoint auth.ts router.get improper authorization — maxun 6.3 Medium2025-12-27
CVE-2025-15087 youlaitech youlai-mall OrderController.java submitOrderPayment improper authorization — youlai-mall 4.3 Medium2025-12-25
CVE-2025-15085 youlaitech youlai-mall Balance MemberController.java deductBalance improper authorization — youlai-mall 4.3 Medium2025-12-25
CVE-2025-68481 FastAPI Users Vulnerable to 1-click Account Takeover in Apps Using FastAPI SSO — fastapi-users 5.9 Medium2025-12-19
CVE-2025-14546 FastAPI SSO 安全漏洞 — fastapi-sso 6.3 Medium2025-12-19
CVE-2025-65041 Microsoft Partner Center Elevation of Privilege Vulnerability — Microsoft Partner Center 10.0 Critical2025-12-18
CVE-2025-14889 Campcodes Advanced Voting Management System Password voters_edit.php improper authorization — Advanced Voting Management System 5.4 Medium2025-12-18
CVE-2023-53895 PimpMyLog 1.7.14 Improper Access Control via Account Creation Endpoint — PimpMyLog 9.8 Critical2025-12-16
CVE-2025-40830 Siemens SINEC Security Monitor 授权问题漏洞 — SINEC Security Monitor 6.7 Medium2025-12-09
CVE-2025-14206 SourceCodester Online Student Clearance System Fee Table delete-fee.php improper authorization — Online Student Clearance System 6.5 Medium2025-12-08
CVE-2025-12720 g-FFL Cockpit <= 1.7.1 - Improper Authorization to Unauthenticated Product Deletion — g-FFL Cockpit 5.3 Medium2025-12-06
CVE-2025-12505 weDocs <= 2.1.14 - Missing Authorization to Settings Update — weDocs: AI Powered Knowledge Base, Docs, Documentation, Wiki & AI Chatbot 5.4 Medium2025-12-06
CVE-2025-14089 Himool ERP AdminActionViewSet update_account improper authorization — ERP 6.3 Medium2025-12-05
CVE-2025-14088 ketr JEPaaS load improper authorization — JEPaaS 6.3 Medium2025-12-05
CVE-2025-14016 macrozheng mall-swarm delete improper authorization — mall-swarm 5.4 Medium2025-12-04
CVE-2025-66301 Grav ihas Broken Access Control which allows an Editor to modify the page's YAML Frontmatter to alter form processing actions — grav 4.3AIMediumAI2025-12-01
CVE-2025-13808 orionsec orion-ops User Profile UserController.java update improper authorization — orion-ops 7.3 High2025-12-01

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