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-27912 Windows Kerberos Elevation of Privilege Vulnerability — Windows Server 2012 8.0 High2026-04-14
CVE-2026-6105 perfree go-fastdfs-web doInstall InstallController.java improper authorization — go-fastdfs-web 7.3 High2026-04-11
CVE-2026-32252 Chartbrew Cross-Tenant Template Export and Secret Disclosure in `GET /team/:team_id/template/generate/:project_id` — chartbrew 7.7 High2026-04-10
CVE-2026-5412 Juju CloudSpec API could leak senstive information — Juju 9.9 Critical2026-04-10
CVE-2026-5999 JeecgBoot SysAnnouncementController improper authorization — JeecgBoot 6.3 Medium2026-04-10
CVE-2026-39901 monetr: Protected Transactions Deletable via PUT — monetr 5.7 Medium2026-04-08
CVE-2026-35479 InvenTree Plugin Installation - Insufficient Permissions — InvenTree 6.6 Medium2026-04-08
CVE-2026-35476 InvenTree Affected by Privilege Escalation via API — InvenTree 7.2 High2026-04-08
CVE-2026-35407 Saleor has Cross-Account Email Change via Unbound Confirmation Token — saleor 5.3AIMediumAI2026-04-08
CVE-2026-39389 CI4MS has a Hidden Items Authorization Bypass in Fileeditor Allows Reading Secrets and Writing Protected Files — ci4ms 6.7 Medium2026-04-08
CVE-2026-39347 OrangeHRM's Self‑Appraisal Submission of Admin Users Can Be Modified After Completion — orangehrm 5.5AIMediumAI2026-04-07
CVE-2026-35610 PolarLearn has a Server Action Admin Bypass in Account Management Actions — PolarLearn 8.8 High2026-04-07
CVE-2026-5642 Cyber-III Student-Management-System HTTP POST Request update.php improper authorization — Student-Management-System 7.3 High2026-04-06
CVE-2026-5529 Dromara lamp-cloud DefUserController pageUser improper authorization — lamp-cloud 4.3 Medium2026-04-05
CVE-2017-20238 Hirschmann Industrial HiVision Improper Authorization Privilege Escalation — Hirschmann Industrial HiVision 7.1 High2026-04-03
CVE-2026-33105 Microsoft Azure Kubernetes Service Elevation of Privilege Vulnerability — Azure Kubernetes Service 10.0 Critical2026-04-02
CVE-2026-32213 Azure AI Foundry Elevation of Privilege Vulnerability — Azure AI Foundry 10.0 Critical2026-04-02
CVE-2026-33950 signalk-server: Privilege Escalation by Admin Role Injection via /enableSecurity — signalk-server 9.4 Critical2026-04-02
CVE-2026-34222 Open WebUI has Broken Access Control in Tool Valves — open-webui 7.7 High2026-04-01
CVE-2026-34738 AVideo: Video Publishing Workflow Bypass via Unauthorized overrideStatus Request Parameter — AVideo 4.3 Medium2026-03-31
CVE-2026-34784 Parse Server: Streaming file download bypasses afterFind file trigger authorization — parse-server 7.5 -2026-03-31
CVE-2026-32619 Discourse: Insufficient topic visibility check allows unauthorized poll manipulation in private categories — discourse 5.4 -2026-03-31
CVE-2026-32615 Discourse: Category group moderators can perform actions on topics in restricted categories without read access — discourse 7.1 -2026-03-31
CVE-2026-4818 Some management operations on data streams are not properly restricted when user does not have the necessary privileges — Search Guard FLX 6.8 Medium2026-03-31
CVE-2026-1710 WooPayments <= 10.5.1 - Missing Authorization to Unauthenticated Plugin Settings Update via save_upe_appearance_ajax — WooPayments: Integrated WooCommerce Payments 6.5 Medium2026-03-31
CVE-2026-32716 SciTokens: Authorization Bypass via Incorrect Scope Path Prefix Checking — scitokens 8.1 High2026-03-31
CVE-2026-30878 baserCMS: Mail Form Acceptance Bypass via Public API — basercms 5.3 Medium2026-03-31
CVE-2026-4248 Ultimate Member <= 2.11.2 - Authenticated (Contributor+) Sensitive Information Exposure to Account Takeover via Shortcode Template Tag — Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin 8.0 High2026-03-27
CVE-2026-4990 chatwoot Signup Endpoint login improper authorization — chatwoot 7.3 High2026-03-27
CVE-2026-33954 LinkAce discloses private notesto unauthorized authenticated users via the web link detail page — LinkAce 6.5 Medium2026-03-27

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