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-112785 OpenCATS before 0.10.0 Missing Authorization in Saved-List AJAX Endpoints — OpenCATS 4.3 Medium 2026-10-20
CVE-2026-112783 OpenCATS before 0.10.0 Missing Authorization via Activity AJAX Endpoints — OpenCATS 4.3 Medium 2026-10-20
CVE-2026-112784 OpenCATS before 0.10.0 Missing Authorization via ajax/testEmailSettings.php — OpenCATS 4.3 Medium 2026-10-20
CVE-2026-112065 Missing Authorization in extension "sgalinski Cookie Consent" (sg_cookie_optin) — Extension "sgalinski Cookie Consent" 5.3 Medium 2026-10-20
CVE-2026-112069 Broken Access Control in extension "FAL Protect" (fal_protect) — Extension "FAL Protect" 6.3 Medium 2026-10-20
CVE-2026-112066 Missing Authorization in extension "sgalinski Cookie Consent" (sg_cookie_optin) — Extension "sgalinski Cookie Consent" 7.1 High 2026-10-20
CVE-2026-112071 Broken Access Control in extension "TYPO3 Shop by coding.ms" (shop) — Extension "TYPO3 Shop by coding.ms" 6.9 Medium 2026-10-20
CVE-2026-113468 Broken Access Control in extension "TYPO3 Shop by coding.ms" (shop) — Extension "TYPO3 Shop by coding.ms" 6.9 Medium 2026-10-20
CVE-2026-112239 Broken Access Control in extension "TYPO3 AI Integration Extension" (ns_t3ai) — Extension "TYPO3 AI Integration Extension" 7.2 High 2026-10-20
CVE-2026-112070 Broken Access Control in extension "Analytics" (analytics) — Extension "Analytics" 5.3 Medium 2026-10-20
CVE-2026-77930 EvoScientist 0.1.0 before 0.2.5 Human Approval Bypass via Async Sub-Agents — EvoScientist 9.8 Critical 2026-10-20
CVE-2026-109444 OpenSRE through 0.1.2026.10.19 Approval Gate Bypass via shell_run Prompt Injection — opensre 9.8 Critical 2026-10-20
CVE-2026-112778 Traefik before 2.11.46, 3.6.17, and 3.7.1 Cross-Namespace Resource Reference via Kubernetes Annotations — traefik 6.4 Medium 2026-10-19
CVE-2025-7043 Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption — WSO2 API Manager 5.4 Medium 2026-10-19
CVE-2026-111058 Mercury: Unauthenticated Remote Code Execution via /api/kernels — mercury 9.8 Critical 2026-10-19
CVE-2026-111046 FOSSBilling: Low-privileged staff can read and modify configuration of deactivated extensions — FOSSBilling 2.3 Low 2026-10-19
CVE-2026-107566 Missing Authorization in hMailServer — hMailServer 6.5 Medium 2026-10-19
CVE-2026-107568 Missing Authorization in hMailServer — hMailServer 6.5 Medium 2026-10-19
CVE-2026-109431 Camunda Missing Authorization in Task Sub-Resources — Camunda 7 8.1 High 2026-10-19
CVE-2026-112329 Sensei LMS 4.26.4 Broken Access Control via save_new_message — Sensei LMS 4.3 Medium 2026-10-19
CVE-2026-112328 Sensei LMS 4.26.4 Broken Access Control via add_new_module_term AJAX — Sensei LMS 4.3 Medium 2026-10-19
CVE-2026-112293 BoxyHQ SaaS Starter Kit through 1.6.0 Missing Authorization on Team Payment API — saas-starter-kit 5.4 Medium 2026-10-19
CVE-2026-112292 CheckCle through 1.6.0 Missing Authorization via Empty PocketBase API Rules — checkcle 9.8 Critical 2026-10-19
CVE-2026-112291 Flarum Extension Manager 2.0.0-beta.1 before 2.0.0-beta.8 Missing Authorization via Task API — Extension Manager 5.3 Medium 2026-10-19
CVE-2026-112262 RisingWave before 3.1.0 Missing Authorization via posix_fs and fs Connectors — risingwave 7.1 High 2026-10-19
CVE-2026-111938 Frappe CRM before 1.74.0 Missing Authorization via add_note_to_call_log — crm 4.3 Medium 2026-10-19
CVE-2026-111937 Frappe CRM before 1.81.2 Missing Authorization on CRM Notification Records — crm 5.4 Medium 2026-10-19
CVE-2026-112222 WordPress Surfer plugin <= 1.8.0.744 - Broken Access Control vulnerability — Surfer 5.4 Medium 2026-10-19
CVE-2026-111845 WordPress YITH WooCommerce Product Bundles plugin <= 2.29.0 - Broken Access Control vulnerability — YITH WooCommerce Product Bundles 5.3 Medium 2026-10-19
CVE-2026-111831 WordPress FluentForm plugin <= 6.2.15 - Broken Access Control vulnerability — FluentForm 5.3 Medium 2026-10-19

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