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-87943 SAML SSO - Service Provider - Critical - Improper access control - SA-CONTRIB-2026-141 — SAML SSO - Service Provider - - 2026-10-22
CVE-2026-87954 Taxonomy Term Glossary - Critical - Access bypass - SA-CONTRIB-2026-152 — Taxonomy Term Glossary - - 2026-10-22
CVE-2026-87955 Ultimate Table Field - Critical - Access bypass - SA-CONTRIB-2026-153 — Ultimate Table Field - - 2026-10-22
CVE-2026-96391 Webform REST - Less critical - Access bypass - SA-CONTRIB-2026-186 — Webform REST - - 2026-10-22
CVE-2026-96380 CSS Usage Analyzer - Moderately critical - Improper access control - SA-CONTRIB-2026-189 — CSS Usage Analyzer - - 2026-10-22
CVE-2026-96386 Smart Content - Moderately critical - Access bypass - SA-CONTRIB-2026-190 — Smart Content - - 2026-10-22
CVE-2026-76308 Missing Authorization through the REST API in Splunk SOAR — Splunk SOAR 6.5 Medium 2026-10-21
CVE-2026-76305 Improper Access Control during App Downloads in Splunk SOAR — Splunk SOAR 6.5 Medium 2026-10-21
CVE-2026-76304 Sensitive Information Disclosure through Automation Broker Configuration in Splunk SOAR — Splunk SOAR 4.3 Medium 2026-10-21
CVE-2026-76296 Missing Authorization through Sourcetype Renaming in Splunk Web for Splunk Enterprise — Splunk Enterprise 4.3 Medium 2026-10-21
CVE-2026-76294 Improper Access Control in Field Extraction Management in Splunk Enterprise — Splunk Enterprise 4.3 Medium 2026-10-21
CVE-2026-76292 Missing Authorization through REST API Endpoints in Splunk Secure Gateway — Splunk Enterprise 6.5 Medium 2026-10-21
CVE-2026-114135 Jupyter Server: Gateway WebSocket handler bypasses kernel execute authorization — jupyter_server 8.8 High 2026-10-21
CVE-2026-114267 SourceCodester Food Order Management System Admin Endpoint authorization — Food Order Management System 7.3 High 2026-10-21
CVE-2026-19947 Missing kernel object permission check in devmux syscalls allows unprivileged user threads to retarget a device multiplexer — zephyr 5.3 Medium 2026-10-21
CVE-2026-105937 Apache Pulsar: Missing authorization of the shadow topic source allows cross-tenant message disclosure and deletion of source topic data — Apache Pulsar 8.7 High 2026-10-21
CVE-2026-105936 Apache Pulsar: Functions connectors list endpoint does not apply the super-user check of the worker connectors endpoint — Apache Pulsar 5.3 Medium 2026-10-21
CVE-2026-105935 Apache Pulsar: Function trigger publishes to the input topic without checking the caller's produce permission — Apache Pulsar 4.9 Medium 2026-10-21
CVE-2026-105934 Apache Pulsar: Missing tenant admin authorization check when truncating a partitioned topic — Apache Pulsar 7.2 High 2026-10-21
CVE-2026-105932 Apache Pulsar: Missing topic policy authorization on non-persistent topic entry filter endpoints — Apache Pulsar 2.3 Low 2026-10-21
CVE-2026-105931 Apache Pulsar: Missing authorization on transaction admin endpoints exposes transaction coordinator and transaction statistics of other tenants — Apache Pulsar 2.3 Low 2026-10-21
CVE-2026-114176 WordPress eRoom plugin <= 1.7.1 - Broken Access Control vulnerability — eRoom 4.3 Medium 2026-10-21
CVE-2026-105926 Apache Pulsar: Missing Topic Authorization on Binary Protocol GetSchema and GetOrCreateSchema Commands — Apache Pulsar 5.3 Medium 2026-10-21
CVE-2026-113797 Electron: Extension tabs.query returns tab URLs and titles without the tabs permission — electron 3.1 Low 2026-10-21
CVE-2026-114489 Missing Authorization in hMailServer — hMailServer 8.1 High 2026-10-21
CVE-2026-114477 Missing Authorization in hMailServer — hMailServer 4.3 Medium 2026-10-21
CVE-2026-114475 Missing Authorization in hMailServer — hMailServer 6.5 Medium 2026-10-21
CVE-2026-111835 WordPress BjornTech Swish for WooCommerce plugin <= 3.7.8 - Broken Access Control vulnerability — BjornTech Swish for WooCommerce 6.5 Medium 2026-10-21
CVE-2026-104949 WarehousePG 6-7 版本 gp_add_coordinator_standby 缺少授权漏洞 — WarehousePG 2.3 Low 2026-10-21
CVE-2026-104948 WarehousePG 6.27-7.6 缺失授权漏洞 — WarehousePG 7.1 High 2026-10-21

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