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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8296 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-109637 Frappe ERPNext before 16.14.0 Missing Authorization Allows Master Data Modification — erpnext 6.5 Medium 2026-10-12
CVE-2026-109635 Frappe ERPNext before 15.105.0 Missing Authorization in Document Creation Endpoints — erpnext 4.3 Medium 2026-10-12
CVE-2026-109632 Frappe ERPNext before 15.121.0 Missing Authorization on Certain Endpoints — erpnext 6.5 Medium 2026-10-12
CVE-2026-109630 Frappe ERPNext before 15.121.0 Missing Authorization in Endpoints — erpnext 4.3 Medium 2026-10-12
CVE-2026-109629 Frappe ERPNext before 15.121.3 Missing Authorization in Transactional Email Endpoint — erpnext 4.3 Medium 2026-10-12
CVE-2026-109627 Frappe ERPNext before 15.120.0 Missing Authorization Exposes Financial Data — erpnext 6.5 Medium 2026-10-12
CVE-2026-109628 Frappe ERPNext before 15.121.0 Unauthorized Status Modification via Missing Authorization — erpnext 6.5 Medium 2026-10-12
CVE-2026-109625 Frappe ERPNext before 15.121.3 Missing Authorization Exposes Financial Data — erpnext 6.5 Medium 2026-10-12
CVE-2026-109624 Frappe ERPNext before 15.120.0 Missing Authorization Exposes Personal Data — erpnext 6.5 Medium 2026-10-12
CVE-2026-109623 Frappe ERPNext before 15.121.1 Unauthorized Document Modification via Missing Authorization — erpnext 5.4 Medium 2026-10-12
CVE-2026-109622 Frappe ERPNext before 15.121.0 Unauthorized Document Modification via Missing Authorization — erpnext 4.3 Medium 2026-10-12
CVE-2026-109621 Frappe ERPNext before 15.120.0 Unauthorized Party Record Access via Permission Bypass — erpnext 6.5 Medium 2026-10-12
CVE-2026-109617 Frappe ERPNext before 15.121.0 Missing Authorization in Record Creation Endpoints — erpnext 7.1 High 2026-10-12
CVE-2026-109616 Frappe ERPNext before 15.121.3 Missing Authorization Allows Unauthorized Data Modification — erpnext 7.1 High 2026-10-12
CVE-2026-109615 Frappe ERPNext before 15.121.0 Missing Authorization in Document Creation Endpoints — erpnext 6.5 Medium 2026-10-12
CVE-2026-109614 Frappe ERPNext before 16.34.0 Missing Authorization Exposes Financial Data — erpnext 6.5 Medium 2026-10-12
CVE-2026-109613 Frappe ERPNext before 15.121.0 Missing Authorization Allows Unauthorized Status Modification — erpnext 7.1 High 2026-10-12
CVE-2026-109610 Frappe ERPNext before 15.119.1 Missing Authorization Allows Unauthorized Document Modification — erpnext 6.5 Medium 2026-10-12
CVE-2026-109611 Frappe ERPNext before 15.121.0 Missing Authorization in Certain Endpoints — erpnext 4.3 Medium 2026-10-12
CVE-2026-109600 Frappe before 16.31.0 Improper Access Control in Document Follow Notifications — frappe 5.3 Medium 2026-10-12
CVE-2026-109598 Frappe before 16.33.0 Broken Authorization via send_sms Endpoint — frappe 4.3 Medium 2026-10-12
CVE-2026-109599 Frappe before 15.113.3 Missing Authorization Allows Unauthorized Record Modification — frappe 4.3 Medium 2026-10-12
CVE-2026-109572 Open WebUI 0.8.6 before 0.11.4 Privilege Escalation via Terminal Proxy — open-webui 7.6 High 2026-10-12
CVE-2026-102596 Nango: Production flow RBAC bypass on private flow-read routes — nango 4.3 Medium 2026-10-12
CVE-2026-109564 LearnHouse before 1.4.0 Missing Authorization via Playground Duplicate Endpoint — LearnHouse 3.1 Low 2026-10-12
CVE-2026-109562 SnapOtter 1.15.10 through 2.2.0 Missing Authorization via Upload and Preview API — SnapOtter 5.4 Medium 2026-10-12
CVE-2026-109377 ERPNext 9.0.0 through 16.50.0 Missing Authorization in Batch Lookup Methods — ERPNext 4.3 Medium 2026-10-12
CVE-2026-84315 Nginx UI OTP secure-session step-up is missing on sensitive mutation routes — nginx-ui 8.3 High 2026-10-12
CVE-2026-61994 WordPress WP-Members plugin <= 3.5.7 - Broken Access Control vulnerability — WP-Members 5.4 Medium 2026-10-12
CVE-2026-108486 WordPress Forminator plugin <= 1.58.0 - Broken Access Control vulnerability — Forminator 5.3 Medium 2026-10-12

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