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 986

986 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-2025-12367 SiteSEO – SEO Simplified <= 1.3.1 - Missing Authorization to Authenticated (Author+) Plugin Settings Update — SiteSEO – SEO Simplified 4.3 Medium2025-11-01
CVE-2025-11174 Document Library Lite <= 1.1.6 - Missing Authorization to Sensitive Information Exposure — Document Library Lite 5.3 Medium2025-11-01
CVE-2025-12304 dulaiduwang003 TIME-SEA-PLUS Order Status PayController.java alipayIsSucceed improper authorization — TIME-SEA-PLUS 4.3 Medium2025-10-27
CVE-2025-12005 WP VR – 360 Panorama and Free Virtual Tour Builder For WordPress <= 8.5.41 - Improper Authorization to Authenticated (Contributor+) Plugin Settings Update — WP VR – 360 Panorama and Free Virtual Tour Builder For WordPress 4.3 Medium2025-10-25
CVE-2025-6639 Tutor LMS Pro – eLearning and online course solution <= 3.8.3 - Authenticated (Subscriber+) Insecure Direct Object Reference to View/Edit Other Assignments — Tutor LMS Pro 5.4 Medium2025-10-25
CVE-2025-11879 GenerateBlocks <= 2.1.1 - Improper Authorization to Authenticated (Contributor+) Arbitrary Options Disclosure — GenerateBlocks 6.5 Medium2025-10-25
CVE-2025-11244 Password Protected <= 2.7.11 - Unauthenticated Authorization Bypass via IP Address Spoofing — Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content 3.7 Low2025-10-25
CVE-2025-10902 Originality.ai AI Checker <= 1.0.15 - Missing Authorization to Authenticated (Subscriber+) Scan Log Deletion via ' ai_scan_result_remove' — Originality.ai AI Checker 4.3 Medium2025-10-24
CVE-2025-62401 Moodle: possible to bypass timer in timed assignments 5.4 Medium2025-10-23
CVE-2025-62610 Hono Improperly Authorizes JWT Audience Validation — hono 8.1 High2025-10-22
CVE-2025-11256 Kognetiks Chatbot <= 2.3.5 - Missing Authorization to Unauthenticated Limited File Uploads and Conversation Erasing — Kognetiks Chatbot for WordPress 5.3 Medium2025-10-18
CVE-2025-11510 FileBird <= 6.4.9 - Improper Authorization to Authenticated (Author+) Settings Reset — FileBird – WordPress Media Library Folders & File Manager 4.3 Medium2025-10-18
CVE-2025-54822 Fortinet FortiOS和Fortinet FortiProxy 授权问题漏洞 — FortiProxy 4.2 Medium2025-10-14
CVE-2025-61928 Better Auth: Unauthenticated API key creation through api-key plugin — better-auth 7.5AIHighAI2025-10-09
CVE-2025-59271 Redis Enterprise Elevation of Privilege Vulnerability — Azure Cache for Redis Enterprise 8.7 High2025-10-09
CVE-2025-49594 XWiki OIDC Authenticator vulnerable to creation of token for any user with just `view` right — oidc 8.8AIHighAI2025-10-06
CVE-2025-11272 SeriaWei ZKEACMS POST Request UrlRedirectionController.cs Delete improper authorization — ZKEACMS 5.4 Medium2025-10-04
CVE-2025-11227 GiveWP – Donation Plugin and Fundraising Platform <= 4.10.0 - Missing Authorization to Unauthenticated Forms and Campaigns Disclosure — GiveWP – Donation Plugin and Fundraising Platform 6.5 Medium2025-10-04
CVE-2025-11080 zhuimengshaonian wisdom-education ExamInfoController.java selectStudentExamInfoList improper authorization — wisdom-education 4.3 Medium2025-09-27
CVE-2025-11050 Portabilis i-Educar periodo-lancamento improper authorization — i-Educar 6.3 Medium2025-09-27
CVE-2025-11049 Portabilis i-Educar unificacao-aluno improper authorization — i-Educar 6.3 Medium2025-09-27
CVE-2025-11048 Portabilis i-Educar consulta-dispensas improper authorization — i-Educar 6.3 Medium2025-09-26
CVE-2025-11047 Portabilis i-Educar aluno improper authorization — i-Educar 6.3 Medium2025-09-26
CVE-2025-11030 Tutorials-Website Employee Management System HTTP Request all-applied-leave.php improper authorization — Employee Management System 7.3 High2025-09-26
CVE-2025-10992 roncoo roncoo-pay lookupList improper authorization — roncoo-pay 5.3 Medium2025-09-26
CVE-2025-10989 yangzongzhuan RuoYi selectAll improper authorization — RuoYi 6.3 Medium2025-09-26
CVE-2025-10988 YunaiV ruoyi-vue-pro transfer improper authorization — ruoyi-vue-pro 6.3 Medium2025-09-26
CVE-2025-10987 YunaiV yudao-cloud HTTP Request transfer improper authorization — yudao-cloud 6.3 Medium2025-09-26
CVE-2025-10981 JeecgBoot exportXls improper authorization — JeecgBoot 4.3 Medium2025-09-26
CVE-2025-10980 JeecgBoot exportXls improper authorization — JeecgBoot 4.3 Medium2025-09-25

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