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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8311 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-2025-30237 Authentication Bypass via Broken Access Control in Web Server in Multiple TP-Link Aginet Devices — HB810(US2) V1.0/1.6/2.0/2.6 8.7 High 2026-08-10
CVE-2026-72919 Rocket.Chat: Broken Access Control in channels.convertToTeam Allows Unauthorized Conversion of Public Channels into Teams — Rocket.Chat 4.3 Medium 2026-08-10
CVE-2026-72918 Rocket.Chat: Insecure implementation of websocket notifications — Rocket.Chat 5.4 Medium 2026-08-10
CVE-2026-72910 ERPNext: Unauthorised modification of master data due to missing validation — erpnext 7.1 High 2026-08-10
CVE-2026-72906 ERPNext: Unauthorised triggering of automated emails due to missing validation — erpnext 4.3 Medium 2026-08-10
CVE-2026-72883 Dokploy: WebSocket Terminal Missing Service-Level Access Control — dokploy 8.8 High 2026-08-10
CVE-2026-14886 Vault Enterprise vulnerable to cross-namespace entity deletion — Vault Enterprise 8.2 High 2026-08-10
CVE-2026-72866 WebSocket Terminal Auth Bypass — dokploy 8.8 High 2026-08-10
CVE-2026-72864 Dokploy Broken Access Control on docker-container-terminal WebSocket (Member -> Root in Arbitrary Containers) — dokploy 9.9 Critical 2026-08-10
CVE-2026-71962 Flowise 2.2.4 - 3.1.4 Missing Authorization via openai-assistants-file/download — Flowise 7.5 High 2026-08-10
CVE-2026-72900 Metabase information exposure — Metabase 6.5 Medium 2026-08-10
CVE-2026-72732 Discourse: Templates endpoint exposes hidden tag names — discourse 4.3 Medium 2026-08-10
CVE-2026-72723 Discourse: Anonymous sidebar serialization exposes descriptions of category-restricted tags — discourse 5.3 Medium 2026-08-10
CVE-2026-72722 Discourse: Duplicate lookup reveals restricted topic titles through canonicalized URLs — discourse 4.3 Medium 2026-08-10
CVE-2026-72759 cti-transmute Conversion History Authorization Bypass Leads to Sensitive Data Disclosure After Conversion Deletion — cti-transmute 6.9 Medium 2026-08-10
CVE-2026-71959 Bitwarden Server < 2026.7.2 Audit Log Injection via POST /collect — server 5.8 Medium 2026-08-10
CVE-2026-72692 OpenSignLabs opensignserver - Missing Authorization — opensignserver 7.5 High 2026-08-10
CVE-2026-19404 389-ds-base: 389-ds-base: missing authorization allows anonymous clients to start or abort cleanallruv replication maintenance — Red Hat Directory Server 11 6.5 Medium 2026-08-10
CVE-2026-19350 Dolibarr ERP TakePOS invoice.php fail authorization — ERP 6.3 Medium 2026-08-09
CVE-2026-19345 code-projects Task Management System UpdateTaskStatus.php authorization — Task Management System 6.5 Medium 2026-08-09
CVE-2026-47127 Ghostfolio has a Stripe subscription bypass — ghostfolio 6.5 Medium 2026-08-07
CVE-2026-64676 Kata Containers: Unauthorized mem-agent ttRPC methods let an untrusted host tamper with confidential-guest memory — kata-containers 5.7 Medium 2026-08-07
CVE-2026-66061 Home Assistant: iOS Companion app forwards NFC/QR tag scans without confirmation, enabling silent automation execution — core 7.1 High 2026-08-07
CVE-2026-66060 Home Assistant: Unconfirmed NFC/QR tag scans allow silent automation execution by untrusted callers — core 7.1 High 2026-08-07
CVE-2026-19017 Consul vulnerable to partial arbitrary file read via Vault Connect CA provider — Consul 6.8 Medium 2026-08-07
CVE-2026-66058 Frappe: Unrestricted access to a Document Follow API — frappe 5.3 Medium 2026-08-07
CVE-2026-17601 Nexus Repository 3 - Wildcard Privilege Update Self-Escalation to Administrator — Nexus Repository 3 8.9 High 2026-08-07
CVE-2026-54201 TeamDavid: Missing Authorization — TeamDavid 6.9 Medium 2026-08-07
CVE-2026-11907 Stream <= 4.2.0 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via Heartbeat API — Stream – Activity Log & Audit Trail 6.5 Medium 2026-08-07
CVE-2026-14365 TrueBooker <= 1.2.3 - Missing Authorization to Unauthenticated Arbitrary Password Reset via 'truebooker_wp_user_id' — TrueBooker – Appointment Booking and Scheduler System 9.8 Critical 2026-08-07

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