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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8304 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-101063 Obot before v0.23.0 Authentication Bypass via Registry API — obot 5.3 Medium 2026-09-27
CVE-2026-100879 zhistaredu StarTraining dataScope Endpoint SysRoleServiceImpl.java checkRoleAllowed authorization — StarTraining 4.3 Medium 2026-09-27
CVE-2026-101047 Fleet before 4.87.0 Unauthenticated iOS App Download via Predictable URLs — fleet 5.3 Medium 2026-09-27
CVE-2026-100855 AzuraCast before 0.23.6 Missing Permission Check via /play — AzuraCast 6.5 Medium 2026-09-27
CVE-2026-100853 AzuraCast before 0.23.8 On-Demand Download Endpoint Authorization Bypass — AzuraCast 5.9 Medium 2026-09-27
CVE-2026-100854 AzuraCast before 0.23.6 Metadata Injection via Liquidsoap API — AzuraCast 6.3 Medium 2026-09-27
CVE-2026-100744 coollabsio Coolify Route-Level Middleware CanUpdateResource.php authorization — Coolify 7.3 High 2026-09-27
CVE-2026-78582 Missing Authorization in Kibana Leading to Unauthorized Deletion of Data — Kibana 6.5 Medium 2026-09-26
CVE-2026-100634 SiYuan before v3.8.4 Missing Authorization via siyuan-send-windows — siyuan 4.7 Medium 2026-09-26
CVE-2026-100617 Cap-go capgo.app Authorization Bypass via channel_permission_overrides — capgo.app 8.8 High 2026-09-26
CVE-2026-100608 Flowise through 3.1.4 Authorization Bypass via BullMQ Dashboard — Flowise 8.3 High 2026-09-26
CVE-2026-100605 Flowise through 3.1.4 Missing Authorization via Chat Message Routes — Flowise 7.1 High 2026-09-26
CVE-2026-100602 ClawHub Changelog Preview Information Disclosure via Authorization Bypass — clawhub 6.5 Medium 2026-09-26
CVE-2026-100596 OpenClaw before 2026.7.1 Authorization Bypass via MCP Configuration — OpenClaw 8.8 High 2026-09-26
CVE-2026-100593 OpenClaw before 2026.7.1 Authentication Bypass via activation — OpenClaw 5.4 Medium 2026-09-26
CVE-2026-100592 OpenClaw before 2026.7.1 Authentication Bypass via Memory Dreaming — OpenClaw 6.3 Medium 2026-09-26
CVE-2026-100591 OpenClaw before 2026.7.1 Authentication Bypass via Active Memory — OpenClaw 6.3 Medium 2026-09-26
CVE-2026-100587 OpenClaw before 2026.7.1 Authorization Bypass via Codex Install — OpenClaw 8.8 High 2026-09-26
CVE-2026-100585 OpenClaw before 2026.7.1 Authentication Bypass via MCP Channel — OpenClaw 8.0 High 2026-09-26
CVE-2026-100583 OpenClaw Discord before 2026.7.1 Authorization Bypass — discord 4.3 Medium 2026-09-26
CVE-2026-100582 OpenClaw Channel Plugins before 2026.8.1 Channel Read Allowlist Bypass — msteams 6.5 Medium 2026-09-26
CVE-2026-100575 OpenClaw Slack before 2026.8.1 Authentication Bypass via Group DM — slack 8.8 High 2026-09-26
CVE-2026-100573 OpenClaw before 2026.8.1 Sandbox Policy Bypass via MCP Loopback — OpenClaw 3.3 Low 2026-09-26
CVE-2026-100544 openclaw voice-call before 2026.8.1 Authorization Bypass — voice-call 8.8 High 2026-09-26
CVE-2026-100537 OpenClaw before 2026.8.1 Authentication Bypass via Active Memory — OpenClaw 3.1 Low 2026-09-26
CVE-2026-100532 openclaw WhatsApp before 2026.8.1 Authentication Bypass — whatsapp 8.1 High 2026-09-26
CVE-2026-100526 Vulnerability in discord — discord 5.3 Medium 2026-09-26
CVE-2026-100525 OpenClaw diagnostics-prometheus before 2026.9.3 Authentication Bypass — diagnostics-prometheus 4.3 Medium 2026-09-26
CVE-2026-63431 Horilla: Missing Authorization on Payroll Component Views Exposes Employee Salary Structures and Personal Loan Records (IDOR) — horilla-hr 6.5 Medium 2026-09-25
CVE-2026-100378 Missing permission check in the Translate sandbox doRemind action — Mediawiki - Translate Extension 5.3 Medium 2026-09-25

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