Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-862 (授权机制缺失) — Vulnerability Class 7017

7017 vulnerabilities classified as CWE-862 (授权机制缺失). AI Chinese analysis included.

CWE-862 represents a critical access control weakness where software fails to verify an actor’s permissions before granting access to resources or executing actions. Attackers typically exploit this flaw by manipulating requests to access sensitive data or perform privileged operations that should be restricted to authorized users. Without proper checks, malicious actors can bypass authentication mechanisms entirely, leading to unauthorized data exposure, modification, or system compromise. Developers mitigate this risk by implementing robust authorization logic at every entry point, ensuring that identity verification is coupled with strict permission validation. This involves checking user roles and access rights against the requested resource before processing any request. By integrating these checks into the application’s core architecture and utilizing established frameworks, teams can prevent unauthorized access and maintain the integrity of their systems against exploitation.

MITRE CWE Description
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Common Consequences (4)
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 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 restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access Control Gain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Availability DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)
An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.
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) [REF-229] 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 …
Architecture and Design Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied 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…
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-84798 Craft CMS before 5.10.11 Authorization Bypass via actionDeleteForSite — cms 7.1 High 2026-09-02
CVE-2026-84797 Craft CMS 5.0.0-RC1 before 5.10.11 Authorization Bypass via actionDuplicate — cms 6.3 Medium 2026-09-02
CVE-2026-84794 Craft CMS 5.0.0 through 5.10.10 Authorization Bypass via assets/move-asset — cms 7.1 High 2026-09-02
CVE-2026-84792 Craft CMS before 5.10.11 Broken Access Control via element-indexes — cms 4.3 Medium 2026-09-02
CVE-2026-14357 DevKit Pro <= 2.3.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Theme Installation / Remote Code Execution via 'qqfile' Parameter — DevKit Pro 8.8 High 2026-09-02
CVE-2026-84715 FeatherPanel before 1.3.7.10 Privilege Escalation via Subuser Permission Update — FeatherPanel 8.8 High 2026-09-02
CVE-2026-84328 Google Chrome 授权问题漏洞 — Chrome - - 2026-09-01
CVE-2026-84323 Google Chrome 授权问题漏洞 — Chrome - - 2026-09-01
CVE-2026-84470 Automation-controller: automation-controller-container: automation-controller/awx: bulk job launch checks instance_groups at read level instead of use level, allowing execution-placement authorization bypass — Red Hat Ansible Automation Platform 2 6.4 Medium 2026-09-01
CVE-2026-78597 Missing Authorization in Kibana Entity Store Leading to Unauthorized API Key Creation — Kibana 4.3 Medium 2026-09-01
CVE-2026-78603 Missing Authorization in Kibana Leading to Unauthorized Disclosure of Fleet Deployment Metadata — Kibana 4.3 Medium 2026-09-01
CVE-2026-78607 Missing Authorization in Elasticsearch Leading to Information Disclosure — Elasticsearch 5.4 Medium 2026-09-01
CVE-2026-78608 Missing Authorization in Kibana Leading to Information Disclosure — Kibana 6.5 Medium 2026-09-01
CVE-2026-84204 GROWI through 8.0.2 Missing Authorization on apiv3 Attachment Retrieval — growi 6.5 Medium 2026-09-01
CVE-2026-19948 Cozy Blocks <= 2.2.17 - Missing Authorization to Unauthenticated Unpublished Product Information Disclosure via 'wishlistData' Parameter — Cozy Blocks – Page Builder for Gutenberg Editor & FSE with 700+ Patterns, 58 Blocks & Templates 5.3 Medium 2026-09-01
CVE-2026-82746 Ash.update_many/4 atomic path skips resource policy authorization, allowing updates to forbidden records — ash 5.9 Medium 2026-09-01
CVE-2026-82394 Sulu: Fix authorization bypass when creating preview links — sulu 5.3 Medium 2026-08-31
CVE-2026-82882 Devtron through 2.2.0 Missing Authorization via webhook API token endpoint — devtron 8.8 High 2026-08-31
CVE-2026-71415 Kirby: File upload permissions are not checked during processing of chunk data — kirby 7.1 High 2026-08-31
CVE-2026-81278 WordPress Post SMTP plugin 4.0.0-beta.1 - Settings Change vulnerability — Post SMTP 5.4 Medium 2026-08-31
CVE-2026-81758 WordPress OwnerRez API plugin <= 1.2.6 - Broken Access Control vulnerability — OwnerRez API 6.3 Medium 2026-08-31
CVE-2026-81762 WordPress Booking and Rental Manager plugin <= 2.7.6 - Broken Access Control vulnerability — Booking and Rental Manager 6.5 Medium 2026-08-31
CVE-2026-81296 WordPress Fluent Forms Pro Add On Pack plugin <= 6.2.12 - Broken Access Control vulnerability — Fluent Forms Pro Add On Pack 7.5 High 2026-08-31
CVE-2026-52730 Xibo CMS Missing Authorization in Module::settingsForm due to PHP operator precedence — xibo-cms 4.3 Medium 2026-08-31
CVE-2026-79745 MCPHub: Missing Authorization on Built-in Prompt & Resource CRUD (Unauthorized Tampering of Globally-Served Templates/Resources) — mcphub 7.1 High 2026-08-31
CVE-2026-79748 MCPHub: Authenticated non-admin user achieves RCE via POST /api/servers (missing authorization on stdio command/args) — mcphub 9.9 Critical 2026-08-31
CVE-2026-77966 Ebyte NA111-M Missing Authorization — Ebyte NA111-M Firmware 8.8 High 2026-08-31
CVE-2026-19616 Information Disclosure in TBC Technology's KitLogistic — KitLogistic 7.5 High 2026-08-31
CVE-2026-74010 WordPress bbPress plugin <= 2.6.14 - Broken Access Control vulnerability — bbPress 5.3 Medium 2026-08-31
CVE-2026-82878 DataEase before 2.10.26 Missing Object-Level Authorization on Geographic, Linkage and Chart Endpoints — dataease 6.3 Medium 2026-08-31

Vulnerabilities classified as CWE-862 (授权机制缺失) represent 7017 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.