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-105621 jishenghua jshERP Financial Receipt Update AccountHeadService.java updateAccountHeadAndDetail improper authorization — jshERP 5.4 Medium 2026-10-06
CVE-2026-105611 chillzhuang SpringBlade User Detail Endpoint RoleController.java improper authorization — SpringBlade 2.7 Low 2026-10-06
CVE-2026-105610 chillzhuang SpringBlade Parameter Submit Management ParamController.java improper authorization — SpringBlade 4.7 Medium 2026-10-06
CVE-2026-105571 PickMall Lilishop Mobile Binding bindMobile improper authorization — PickMall Lilishop 7.3 High 2026-10-06
CVE-2026-105382 onetwothreeneth HospitalManagementSystem Account Administration controller.php update_subaccount improper authorization — HospitalManagementSystem 7.3 High 2026-10-05
CVE-2026-105284 Totolink A3002MU Authentication Check boa sub_40FCFC improper authorization — A3002MU 10.0 Critical 2026-10-05
CVE-2026-105121 OpenAM before 16.1.3 Improper Authorization in Delegated Session-Destroy Realm Scoping — OpenAM 4.9 Medium 2026-10-03
CVE-2026-105119 OpenAM before 16.1.3 PKCE Enforcement Bypass via OAuth 2.0 Hybrid Flows — OpenAM 6.8 Medium 2026-10-03
CVE-2026-103858 MISP Incomplete Thread Authorization Allows Unauthorized Read and Post Access to Discussions — MISP 5.3 Medium 2026-10-01
CVE-2026-103532 immich-app Immich Shared Link Preview access.ts checkSharedLinkAccess improper authorization — Immich 5.3 Medium 2026-10-01
CVE-2026-93547 Missing Authorization Check in Vaadin Spreadsheet Allows Cell Comments to Be Written to Protected Sheets and Locked Cells — vaadin 5.3 Medium 2026-09-30
CVE-2026-13720 Editor can forge file-provisioning provenance on dashboards via the dashboard API — Grafana OSS 5.4 Medium 2026-09-30
CVE-2026-102846 gedelumbung HospitalManagement Configuration sistem.php simpan improper authorization — HospitalManagement 4.7 Medium 2026-09-30
CVE-2026-86101 Fireware OS Authorization Bypass in SAML Login Allows Unauthorized SSLVPN Access — Fireware OS 7.2 High 2026-09-29
CVE-2026-102293 realjerrytang tacomall api-admin Backend ApiMaApplication.java OrgStaffServiceImpl.add improper authorization — tacomall 7.3 High 2026-09-29
CVE-2025-71426 Contrast before 1.4.1 Coordinator Impersonation via Unauthenticated Recovery — contrast 7.1 High 2026-09-27
CVE-2026-55217 GLPI: Unallowed modfication of knowbase items comments and translations — glpi 5.3 Medium 2026-09-25
CVE-2026-53628 GLPI: Unallowed authentication method update by administrator — glpi 5.9 Medium 2026-09-25
CVE-2026-61837 RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks — rabbitmq-server 6.3 Medium 2026-09-25
CVE-2026-96448 Keycloak-services: keycloak-services: fgap v2 composite-blind role mapping allows privilege escalation — Red Hat Build of Keycloak 6.6 Medium 2026-09-25
CVE-2026-92799 Online Scheduling and Appointment Booking System <= 28.2 - Unauthenticated Authorization Bypass via PHP Type Juggling via 'verification_code' Parameter Type Juggling via json_data — Online Scheduling and Appointment Booking System – Bookly 5.3 Medium 2026-09-25
CVE-2026-97324 YunaiV/zhijiantianya ruoyi-vue-pro Demo-order Payment Callback PayDemoOrderController.java updateDemoOrderPaid improper authorization — ruoyi-vue-pro 7.3 High 2026-09-24
CVE-2026-61604 ixo Blockchain x/bonds DID-resolved payer drain + x/entity ICA authorization bypass — ixo-blockchain 9.3 Critical 2026-09-24
CVE-2026-96882 TaleLin lin-cms-spring-boot book Endpoint BookController.java searchBook improper authorization — lin-cms-spring-boot 5.3 Medium 2026-09-24
CVE-2026-96881 TaleLin lin-cms-spring-boot book Endpoint BookController.java getBooks improper authorization — lin-cms-spring-boot 5.3 Medium 2026-09-24
CVE-2026-96880 TaleLin lin-cms-spring-boot book Endpoint BookController.java getBook improper authorization — lin-cms-spring-boot 5.3 Medium 2026-09-24
CVE-2026-96556 Neethuharii CafeManagement AddCashierCode.php addcashier improper authorization — CafeManagement 7.3 High 2026-09-23
CVE-2026-16346 DataStage on Cloud Pak for Data has several vulnerabilities — DataStage on Cloud Pak for Data 9.9 Critical 2026-09-22
CVE-2026-83805 Nautobot: Authorization bypass in approval workflow REST API allows self-approval and unauthorized activation of scheduled jobs — nautobot 6.4 Medium 2026-09-22
CVE-2026-95805 MISP ACLComponent: Typo in previewEventAttributes ACL key bypasses intended access restriction — MISP 5.3 Medium 2026-09-22

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