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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

1306 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)
Confidentiality Read 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.
Integrity Modify 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 Control Gain 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 Design Divide 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 Design Ensure 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 Design Use 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 Design For 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, Installation Use 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 ID Title CVSS Severity Published
CVE-2026-115477 obsidian-tc: Declined human-in-the-loop confirmations can permit destructive calls over HTTP — obsidian-tc 7.1 High 2026-10-23
CVE-2026-57121 PraisonAI: Missing ownership check on DELETE endpoints allows members to delete others' content in Platform API — PraisonAI 8.1 High 2026-10-23
CVE-2026-114361 HarnessRouter Identity Mode app.py improper authorization — HarnessRouter 5.6 Medium 2026-10-21
CVE-2026-114249 dhikshitha29 Insurance-Management-System Policy Holder Update Form UpdatePolicyHolder-inc.php improper authorization — Insurance-Management-System 7.3 High 2026-10-21
CVE-2026-114245 dhikshitha29 Insurance-Management-System Add New Admin Form Admin-Register-inc.php improper authorization — Insurance-Management-System 7.3 High 2026-10-21
CVE-2026-84748 Apache bRPC: Builtin services reachable from the public port via protobuf protocols despite ServerOptions.internal_port configuration — Apache bRPC - - 2026-10-21
CVE-2026-81212 DataStage on Cloud Pak for Data Improper Authorization — DataStage on Cloud Pak for Data 10.0 Critical 2026-10-20
CVE-2026-112045 donetick History Deletion model.go CanDeleteHistory improper authorization — donetick 5.4 Medium 2026-10-19
CVE-2026-111913 Admidio 5.0.0 before 5.0.16 Authorization Bypass via pdfl Mode in lists_show.php — admidio 4.3 Medium 2026-10-17
CVE-2026-17068 IBM i is Affected By Improper Authorization and Access Control Vulnerabilities in Network File System — i 5.4 Medium 2026-10-16
CVE-2026-17275 IBM i is Affected by an Improper Validation Vulnerability — i 3.7 Low 2026-10-16
CVE-2026-86009 Mailu: Domain managers can allow themselves to spoof on other hosted domains they should not control — Mailu 8.2 High 2026-10-16
CVE-2026-86008 Mailu domain managers can take over higher-privileged accounts — Mailu 7.2 High 2026-10-16
CVE-2026-54657 Open Zaak: /zaken/_zoek and /enkelvoudiginformatieobjecten/_zoek endpoints do not filter result lists based on authorizations linked to token — open-zaak 6.5 Medium 2026-10-16
CVE-2026-54683 NL Portal Backend Libraries: Document contents remained downloadable by any logged-in user until 3.0.3 (incomplete fix of CVE-2026-49463) — nl-portal-backend-libraries 6.5 Medium 2026-10-15
CVE-2026-61838 Lychee: Album password bypass in ZIP downloads — Lychee 8.2 High 2026-10-15
CVE-2026-55383 InvoiceShelf: Public EmailLog token type confusion allows cross-company invoice disclosure — InvoiceShelf 8.2 High 2026-10-14
CVE-2026-70407 Gitea organization listing token scope bypass — Gitea - - 2026-10-14
CVE-2026-109605 SourceCodester Simple Cafe Billing System User Management admin_class.php save_user improper authorization — Simple Cafe Billing System 7.3 High 2026-10-13
CVE-2026-109962 Froxlor 0.10.0 before 2.3.14 Missing Authorization in MysqlServer and Cronjobs API — froxlor 4.3 Medium 2026-10-13
CVE-2026-17475 IBM Planning Analytics Local is affected by security vulnerabilities — Planning Analytics 7.1 High 2026-10-12
CVE-2023-54410 Frappe before 13.22.0 Improper Authorization via Document Rename — frappe 4.3 Medium 2026-10-12
CVE-2026-84314 Nginx UI: Account Takeover via Missing `RequireSecureSession` on User Management Endpoint — nginx-ui 8.7 High 2026-10-12
CVE-2026-108899 tobychui zoraxy Path Exception Matcher authProviders.go handleBasicAuth improper authorization — zoraxy 7.3 High 2026-10-12
CVE-2026-108890 BlackBeltTechnology pi-agent-dashboard Terminal terminal-handler.ts terminalManager.spawn improper authorization — pi-agent-dashboard 6.3 Medium 2026-10-12
CVE-2026-108812 SEMCMS SEMCMS_User.php user improper authorization — SEMCMS 6.5 Medium 2026-10-12
CVE-2026-108575 BerriAI LiteLLM Secret Resolution main.py get_secret improper authorization — LiteLLM 6.3 Medium 2026-10-11
CVE-2026-11930 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access — Security Verify Access 5.9 Medium 2026-10-08
CVE-2026-16181 IBM DataPower Gateway Improper Authorization — DataPower Gateway 10.6CD 7.4 High 2026-10-08
CVE-2026-76275 Improper Authorization in Search Job Listings through the REST API in Splunk Enterprise — Splunk Enterprise 4.3 Medium 2026-10-07

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