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-77795 Dromara RuoYi-Vue-Plus Workflow Endpoint TestLeaveController improper authorization — RuoYi-Vue-Plus 6.3 Medium 2026-08-21
CVE-2026-77686 Dolibarr Account card.php improper authorization — Dolibarr 5.4 Medium 2026-08-21
CVE-2026-66722 Apache CloudStack: ProjectRole & ProjectRolePermission authorization issue — Apache CloudStack - - 2026-08-21
CVE-2026-54624 django CMS: Structure endpoint bypasses page-view permission — django-cms 6.5 Medium 2026-08-20
CVE-2026-77036 elunez eladmin GenConfigController improper authorization — eladmin 6.3 Medium 2026-08-20
CVE-2026-18283 Sony XAV-9500ES udev USB Rules Authorization Bypass Vulnerability — XAV-9500ES - - 2026-08-20
CVE-2026-76999 SourceCodester CET Automated Grading System with AI Predictive Analytics index.php add_grade improper authorization — CET Automated Grading System with AI Predictive Analytics 6.3 Medium 2026-08-20
CVE-2026-16925 Vulnerabilities in IBM AIX and PowerVM VIOS — AIX 7.1 High 2026-08-20
CVE-2026-76352 Improper Authorization through the REST API in Splunk Enterprise — Splunk Enterprise 8.8 High 2026-08-19
CVE-2026-53548 Termix: IDOR — Authenticated user can fetch SSH passwords for hosts owned by other users — Termix 9.6 Critical 2026-08-19
CVE-2026-55519 Snipe-IT: Improper Authorization in File Deletion (IDOR) — snipe-it 5.4 Medium 2026-08-19
CVE-2026-76243 stigmem before 0.9.0a2 Authentication Bypass via Disabled Auth — stigmem 9.2 Critical 2026-08-19
CVE-2025-11729 PPWP: Password Protect Pages, Posts & Full or Partial Content <= 1.9.15 - Improper Authorization To Authenticated (Contributor+) Master Password Exposure — PPWP – Password Protect Pages 4.3 Medium 2026-08-18
CVE-2026-55166 Lemur: any SSO-authenticated user achieves AWS IAM compromise and permanent PKI key access via ACME acme_url SSRF and creator-equality IDOR — lemur 9.9 Critical 2026-08-18
CVE-2026-48744 Saleor: Anonymous users can modify channel settings via `channelUpdate` due to `all([])` bypass in permission check — saleor 6.5 Medium 2026-08-18
CVE-2026-19608 Keycloak-services: keycloak-services: name-only group claims let same-name groups satisfy path-specific group policies — Red Hat Build of Keycloak 5.3 Medium 2026-08-18
CVE-2024-14045 OpenBoxes Product Supplier Edit Controller RoleInterceptor.groovy improper authorization — OpenBoxes 6.3 Medium 2026-08-18
CVE-2026-19986 Adblock for Youtube Extension Event Listener contentscript.js updateDynamicRules improper authorization — Adblock for Youtube Extension 5.4 Medium 2026-08-17
CVE-2026-16879 IBM Db2 Mirror for i is affected by multiple vulnerabilities — Db2 Mirror for i 8.8 High 2026-08-14
CVE-2026-73421 NextAuth.js: Configuration errors can cause existence-based auth checks to fail open (auth object populated with an error) — next-auth 9.1 Critical 2026-08-13
CVE-2026-18509 IBM i is Affected By A Prvilege Escalation Vulnerability [] — i 8.2 High 2026-08-13
CVE-2026-73644 OpenDJ: Authorization bypass in SASL PLAIN allowing a `proxied-auth` holder to impersonate any resolvable non-root user without an ACI proxy grant — OpenDJ 9.6 Critical 2026-08-13
CVE-2026-3835 Prevent Direct Access – Protect WordPress Files <= 2.8.8.8 - Unauthenticated Protected File Access — Prevent Direct Access – Protect WordPress Files 5.3 Medium 2026-08-13
CVE-2026-10543 IBM® Db2® is vulnerable to privilege escalation with a specially crafted query — Db2 8.2 High 2026-08-12
CVE-2026-72786 Craft CMS 5.0.0-RC1 before 5.10.8 Authentication Bypass via Password Reset — cms 6.5 Medium 2026-08-12
CVE-2026-18144 IBM i is Affected By Multiple Vulnerabilities in Navigator for i — i 4.3 Medium 2026-08-12
CVE-2026-18499 IBM WebSphere Application Server Liberty is affected by a privilege escalation — WebSphere Application Server - Liberty 8.1 High 2026-08-12
CVE-2026-72907 ERPNext: Broken Access Control on certain endpoint — erpnext 6.5 Medium 2026-08-10
CVE-2026-47663 Pathling: Typed CRUD/search/batch providers can lead to server-wide PHI exfiltration and cross-resource mutation — pathling 8.7 High 2026-08-07
CVE-2026-59118 Copilot Cowork Elevation of Privilege Vulnerability — Copilot Cowork 9.3 Critical 2026-08-06

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