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 985

985 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-3737 SourceCodester Pet Grooming Management Software User Creation add_user.php improper authorization — Pet Grooming Management Software 6.3 Medium2026-03-08
CVE-2026-3734 SourceCodester Client Database Management System Endpoint fetch_manager_details.php improper authorization — Client Database Management System 7.3 High2026-03-08
CVE-2026-3724 SourceCodester Patients Waiting Area Queue Management System checkin.php improper authorization — Patients Waiting Area Queue Management System 6.3 Medium2026-03-08
CVE-2026-3675 Freedom Factory dGEN1 org.ethosmobile.ethoslauncher FakeAppReceiver improper authorization — dGEN1 5.3 Medium2026-03-07
CVE-2026-3674 Freedom Factory dGEN1 org.ethosmobile.ethoslauncher FakeAppProvider improper authorization — dGEN1 5.3 Medium2026-03-07
CVE-2026-3671 Freedom Factory dGEN1 org.ethereumphone.walletmanager.testing123 TokenBalanceContentProvider improper authorization — dGEN1 3.3 Low2026-03-07
CVE-2026-3670 Freedom Factory dGEN1 com.dgen.alarm improper authorization — dGEN1 5.3 Medium2026-03-07
CVE-2026-3669 Freedom Factory dGEN1 com.dgen.alarm AlarmService improper authorization — dGEN1 5.3 Medium2026-03-07
CVE-2026-3667 Freedom Factory dGEN1 org.ethosmobile.ethoslauncher FakeAppService improper authorization — dGEN1 5.3 Medium2026-03-07
CVE-2026-28685 Kimai: API invoice endpoint missing customer-level access control (IDOR) — kimai 6.5 Medium2026-03-06
CVE-2026-28448 OpenClaw 2026.1.29 < 2026.2.1 - Authorization Bypass in Twitch Plugin allowFrom Access Control — OpenClaw 7.3 High2026-03-05
CVE-2026-30793 RustDesk Flutter URI Handler Sets Permanent Password Without Privilege Check or User Confirmation — RustDesk Client 8.8 -2026-03-05
CVE-2026-3265 go2ismail Free-CRM Security API improper authorization — Free-CRM 6.3 Medium2026-02-26
CVE-2026-3263 go2ismail Asp.Net-Core-Inventory-Order-Management-System Security API improper authorization — Asp.Net-Core-Inventory-Order-Management-System 6.3 Medium2026-02-26
CVE-2026-2694 The Events Calendar <= 6.15.16 - Improper Authorization to Authenticated (Contributor+) Event/Organizer/Venue Update/Trash via REST API — The Events Calendar 5.4 Medium2026-02-25
CVE-2026-24890 OpenEMR Portal Users Can Forge Provider Signatures — openemr 8.1 High2026-02-25
CVE-2026-2896 funadmin Configuration Ajax.php setConfig improper authorization — funadmin 7.3 High2026-02-21
CVE-2026-2860 feng_ha_ha/megagao ssm-erp/production_ssm EmployeeController.java improper authorization — ssm-erp 6.3 Medium2026-02-21
CVE-2026-2733 Org.keycloak/keycloak-services: keycloak: missing check on disabled client for docker registry protocol — Red Hat build of Keycloak 26.4 3.8 Low2026-02-19
CVE-2025-4521 IDonate 2.1.5 - 2.1.9 - Missing Authorization to Authenticated (Subscriber+) Account Takeover/Privilege Escalation via idonate_donor_profile Function — IDonate – Blood Donation, Request And Donor Management System 8.8 High2026-02-19
CVE-2026-2693 CoCoTeaNet CyreneAdmin System Info Endpoint getCount improper authorization — CyreneAdmin 4.3 Medium2026-02-19
CVE-2026-2676 GoogTech sms-ssm API LoginInterceptor.java preHandle improper authorization — sms-ssm 6.3 Medium2026-02-18
CVE-2026-26020 AutoGPT Affected by Remote Code Execution via Dynamic Module Import in Block Loading (__import__) — AutoGPT 8.8AIHighAI2026-02-12
CVE-2026-25999 Klaw has an improper authorisation check on /resetMemoryCache — klaw 7.1 High2026-02-11
CVE-2026-25893 FUXA Unauthenticated Remote Code Execution via Admin JWT Minting — FUXA 9.8AICriticalAI2026-02-09
CVE-2026-25885 PolarLearn allows Unauthenticated WebSocket access allows subscribing to and posting in arbitrary group chats — PolarLearn 6.5AIMediumAI2026-02-09
CVE-2026-25809 PlaciPy Code Execution Allowed Without Assessment Active State Validation — assessment-placipy 9.8AICriticalAI2026-02-09
CVE-2026-2141 WuKongOpenSource WukongCRM URL PermissionServiceImpl.java improper authorization — WukongCRM 6.3 Medium2026-02-08
CVE-2026-2209 WeKan Custom Translation translationBody.js setCreateTranslation improper authorization — WeKan 6.3 Medium2026-02-08
CVE-2026-2109 jsbroks COCO Annotator Delete Category undo improper authorization — COCO Annotator 5.4 Medium2026-02-07

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