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-3014 Insecure direct object references (IDOR) in NightWolf Penetration Platform — NightWolf Penetration Platform 8.1 -2025-03-31
CVE-2025-3013 Insecure direct object references (IDOR) in NightWolf Penetration Platform — NightWolf Penetration Platform 8.1 -2025-03-31
CVE-2025-2600 Devolutions Remote Desktop Manager 安全漏洞 — Remote Desktop Manager 8.8AIHighAI2025-03-26
CVE-2025-2528 Devolutions Remote Desktop Manager 安全漏洞 — Remote Desktop Manager 8.8AIHighAI2025-03-26
CVE-2025-29778 Kyverno ignores subjectRegExp and IssuerRegExp — kyverno 5.8 Medium2025-03-24
CVE-2025-2653 FoxCMS improper authorization — FoxCMS 4.3 Medium2025-03-23
CVE-2025-2639 JIZHICMS Article release.html improper authorization — JIZHICMS 4.3 Medium2025-03-23
CVE-2025-2638 JIZHICMS Article release.html improper authorization — JIZHICMS 4.3 Medium2025-03-23
CVE-2025-2637 JIZHICMS Account Profile Page userinfo.html improper authorization — JIZHICMS 4.3 Medium2025-03-23
CVE-2025-29927 Authorization Bypass in Next.js Middleware — next.js 9.1 Critical2025-03-21
CVE-2025-2589 code-projects Human Resource Management System Account.go Index improper authorization — Human Resource Management System 5.5 Medium2025-03-21
CVE-2025-29922 kcp allows unauthorized creation and deletion of objects in arbitrary workspaces through APIExport Virtual Workspace — kcp 9.6 Critical2025-03-20
CVE-2025-29926 The WikiManager REST API allows any user to create wikis — xwiki-platform 8.8 -2025-03-19
CVE-2025-2397 China Mobile P22g-CIac Telnet Service improper authorization — P22g-CIac 2.4 Low2025-03-17
CVE-2025-2360 D-Link DIR-823G UPnP Service HNAP1 SetUpnpSettings improper authorization — DIR-823G 7.3 High2025-03-17
CVE-2025-2359 D-Link DIR-823G DDNS Service HNAP1 SetDDNSSettings improper authorization — DIR-823G 7.3 High2025-03-17
CVE-2025-2345 IROAD Dash Cam X5/Dash Cam X6 improper authorization — Dash Cam X5 9.8 Critical2025-03-16
CVE-2025-2320 274056675 springboot-openai-chatgpt User submit improper authorization — springboot-openai-chatgpt 7.3 High2025-03-14
CVE-2025-24053 Microsoft Dataverse Elevation of Privilege Vulnerability — Microsoft Dataverse 7.2 High2025-03-13
CVE-2025-27602 Umbraco Allows a Restricted Editor User to Delete Media Item or Access Unauthorized Content — Umbraco-CMS 4.9 Medium2025-03-11
CVE-2025-27601 Umbraco Allows Improper API Access Control to Low-Privilege Users to Data Type Functionality — Umbraco-CMS 4.3 Medium2025-03-11
CVE-2025-2114 Shenzhen Sixun Software Sixun Shanghui Group Business Management System Reset Password Interface OperatorStop.asp improper authorization — Sixun Shanghui Group Business Management System 3.7 Low2025-03-09
CVE-2024-13552 SupportCandy – Helpdesk & Customer Support Ticket System <= 3.3.0 - Insecure Direct Object Reference — SupportCandy – Helpdesk & Customer Support Ticket System 4.3 Medium2025-03-07
CVE-2025-27509 SAML authentication vulnerability due to improper SAML response validation — fleet 8.8 -2025-03-06
CVE-2024-13724 Wallet System for WooCommerce – Wallet, Wallet Cashback, Refunds, Partial Payment, Wallet Restriction <= 2.6.2 - Missing Authorization — Wallet System for WooCommerce – Digital Wallet, Buy Now Pay Later (BNPL), Instant Cashback, Referral program, Partial & Subscription Payments 4.3 Medium2025-03-04
CVE-2024-43051 Improper Authorization in SPS-HLOS — Snapdragon 5.5 Medium2025-03-03
CVE-2025-1847 zj1983 zz improper authorization — zz 6.3 Medium2025-03-03
CVE-2025-1815 pbrong hrms resource.go HrmsDB improper authorization — hrms 7.3 High2025-03-02
CVE-2025-1806 Eastnets PaymentSafe URL Default.aspx improper authorization — PaymentSafe 4.3 Medium2025-03-01
CVE-2024-47053 Improper Authorization in Reporting API — mautic/core 7.7 High2025-02-26

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