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-42202 nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields — nova-toggle-5 6.5 Medium2026-05-08
CVE-2026-33823 Microsoft Team Events Portal Information Disclosure Vulnerability — Microsoft Teams 9.6 Critical2026-05-07
CVE-2026-41572 Note Mark: Unauthenticated read of notes and assets in soft-deleted public books — note-mark 5.3 Medium2026-05-04
CVE-2026-7713 crocodilestick Calibre-Web-Automated Kobo auth-token Route kobo_auth.py generate_auth_token improper authorization — Calibre-Web-Automated 6.3 Medium2026-05-04
CVE-2026-7709 janeczku Calibre-Web Endpoint kobo_auth.py generate_auth_token improper authorization — Calibre-Web 6.3 Medium2026-05-03
CVE-2026-7644 ChatGPTNextWeb NextChat actions.ts addMcpServer improper authorization — NextChat 7.3 High2026-05-02
CVE-2026-7631 code-projects Online Hospital Management System Registration improper authorization — Online Hospital Management System 5.4 Medium2026-05-02
CVE-2026-6449 Booking for Appointments and Events Calendar – Amelia <= 2.1.2 - Unauthenticated Authorization Bypass via Remote Approval Endpoint — Booking for Appointments and Events Calendar – Amelia 5.3 Medium2026-05-02
CVE-2026-7602 JeecgBoot FillRuleUtil edit improper authorization — JeecgBoot 6.3 Medium2026-05-02
CVE-2026-7505 nextlevelbuilder GoClaw/GoClaw Lite RPC improper authorization — GoClaw 7.3 High2026-04-30
CVE-2026-2892 Otter Blocks <= 3.1.4 - Improper Authorization to Unauthenticated Purchase Verification Bypass via Forged Cookie — Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE 7.5 High2026-04-30
CVE-2026-7292 o2oa NodeAgent NodeAgent.java syncFile improper authorization — o2oa 5.6 Medium2026-04-28
CVE-2026-5781 Multiple vulnerabilities in MphRx's Minerva — Minerva 8.8AIHighAI2026-04-28
CVE-2026-7142 Wooey API Endpoint scripts.py add_or_update_script improper authorization — Wooey 6.3 Medium2026-04-27
CVE-2026-7109 code-projects Invoice System in Laravel API Endpoint item improper authorization — Invoice System in Laravel 5.3 Medium2026-04-27
CVE-2026-7093 code-projects Invoice System in Laravel Invoice Endpoint invoice improper authorization — Invoice System in Laravel 6.3 Medium2026-04-27
CVE-2026-7092 code-projects Invoice System in Laravel Profile profile improper authorization — Invoice System in Laravel 6.3 Medium2026-04-27
CVE-2026-7091 code-projects Invoice System in Laravel User Management user improper authorization — Invoice System in Laravel 6.3 Medium2026-04-27
CVE-2026-6977 vanna-ai vanna Legacy Flask API improper authorization — vanna 7.3 High2026-04-25
CVE-2026-6634 usememos UpdateInstanceSetting App.tsx memos_access_token improper authorization — memos 6.3 Medium2026-04-20
CVE-2026-6609 liangliangyy DjangoBlog views.py form_valid improper authorization — DjangoBlog 6.3 Medium2026-04-20
CVE-2026-6572 Collabora KodExplorer fileUpload Endpoint share.class.php improper authorization — KodExplorer 5.6 Medium2026-04-19
CVE-2026-6564 EMQ EMQX Enterprise Session Handling improper authorization — EMQX Enterprise 4.3 Medium2026-04-19
CVE-2026-40305 DNN has Force Friend Request Acceptance — Dnn.Platform 4.3 Medium2026-04-17
CVE-2026-40259 SiYuan: Publish Reader Can Arbitrarily Delete Attribute View Files via removeUnusedAttributeView API — siyuan 8.1 High2026-04-16
CVE-2026-40248 free5gc UDR improper path validation allows unauthenticated creation and modification of Traffic Influence Subscriptions — free5gc 7.5AIHighAI2026-04-16
CVE-2026-40247 free5gc UDR improper path validation allows unauthenticated access to Traffic Influence Subscriptions — free5gc 5.3AIMediumAI2026-04-16
CVE-2026-40246 free5gc UDR improper path validation allows unauthenticated deletion of Traffic Influence Subscriptions — free5gc 5.3AIMediumAI2026-04-16
CVE-2026-33146 Docmost's Public Share Search Exposes Metadata of Restricted Children — docmost 4.3 Medium2026-04-14
CVE-2026-34370 Chamilo LMS: IDOR in the Notebook Module allows an attacker to view other users' private notes — chamilo-lms 6.5 Medium2026-04-14

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