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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8303 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-47604 NVIDIA驱动缺失授权检查致信息泄露漏洞 — GeForce 5.5 Medium 2026-09-30
CVE-2026-47603 NVIDIA驱动缺失授权检查致信息泄露漏洞 — GeForce 5.5 Medium 2026-09-30
CVE-2026-47492 NVIDIA驱动内核层访问控制不当致拒绝服务漏洞 — GeForce 5.5 Medium 2026-09-30
CVE-2026-47580 NVIDIA Windows驱动内核模块授权缺失漏洞 — GeForce 7.3 High 2026-09-30
CVE-2026-47559 NVIDIA驱动内核层越界访问致代码执行漏洞 — GeForce 7.8 High 2026-09-30
CVE-2026-47552 NVIDIA Linux驱动内核层越权漏洞 — GeForce 7.8 High 2026-09-30
CVE-2026-100280 JetBrains YouTrack 2026.2前越权创建项目漏洞 — YouTrack 3.1 Low 2026-09-30
CVE-2026-100271 JetBrains YouTrack 2026.2前越权访问漏洞 — YouTrack 2.7 Low 2026-09-30
CVE-2026-100269 JetBrains YouTrack 2026.2前授权报告者列表绕过漏洞 — YouTrack 4.3 Medium 2026-09-30
CVE-2026-100266 JetBrains Hub 2026.2前授权缺失致任意邮件 — Hub 7.7 High 2026-09-30
CVE-2026-97285 WordPress The Events Calendar plugin <= 6.17.5 - Broken Access Control vulnerability — The Events Calendar 5.4 Medium 2026-09-30
CVE-2026-97267 WordPress Prevent files / folders access plugin <= 2.6.7 - Broken Access Control vulnerability — Prevent files / folders access 4.3 Medium 2026-09-30
CVE-2026-97247 WordPress Blocksy Companion plugin <= 2.1.55 - Broken Access Control vulnerability — Blocksy Companion 6.5 Medium 2026-09-30
CVE-2026-97243 WordPress AllAble Connector plugin <= 0.13.4 - Broken Access Control vulnerability — AllAble Connector 5.4 Medium 2026-09-30
CVE-2026-97239 WordPress MCP Content Manager Lite plugin <= 1.1.0 - Broken Access Control vulnerability — MCP Content Manager Lite 6.5 Medium 2026-09-30
CVE-2026-97197 WordPress WordPress Backup & Migration plugin <= 1.6.0 - Broken Access Control vulnerability — WordPress Backup & Migration 7.5 High 2026-09-30
CVE-2026-96834 WordPress GiveWP plugin <= 4.16.9 - Sensitive Data Exposure vulnerability — GiveWP 6.5 Medium 2026-09-30
CVE-2026-96823 WordPress Customer Reviews for WooCommerce plugin <= 5.120.0 - Arbitrary Content Deletion vulnerability — Customer Reviews for WooCommerce 7.5 High 2026-09-30
CVE-2026-96818 WordPress WP Express Checkout (Accept PayPal Payments) plugin <= 2.4.9 - Broken Access Control vulnerability — WP Express Checkout (Accept PayPal Payments) 7.5 High 2026-09-30
CVE-2026-96817 WordPress MakeCommerce for WooCommerce plugin <= 4.1.0 - Broken Access Control vulnerability — MakeCommerce for WooCommerce 8.2 High 2026-09-30
CVE-2026-96348 WordPress Bookly plugin <= 28.2 - Broken Access Control vulnerability — Bookly 7.5 High 2026-09-30
CVE-2026-95587 WordPress Hostinger Migrator plugin <= 1.0 - Broken Access Control vulnerability — Hostinger Migrator 7.5 High 2026-09-30
CVE-2026-94499 WordPress FormGent plugin <= 1.12.2 - Broken Access Control vulnerability — FormGent 7.1 High 2026-09-30
CVE-2026-94120 WordPress GravityExport Lite for Gravity Forms plugin <= 2.7.2 - Broken Access Control vulnerability — GravityExport Lite for Gravity Forms 7.5 High 2026-09-30
CVE-2026-94074 WordPress Simply Schedule Appointments plugin <= 1.6.12.29 - Broken Access Control vulnerability — Simply Schedule Appointments 6.5 Medium 2026-09-30
CVE-2026-96342 WordPress WPMobile.App plugin <= 11.83 - Sensitive Data Exposure vulnerability — WPMobile.App 6.9 Medium 2026-09-30
CVE-2026-81841 Paused shared dashboard access tokens still expose data source configuration — Grafana Enterprise 5.3 Medium 2026-09-29
CVE-2026-102320 Chrome 154前CORS授权缺失致跨域策略绕过 — Chrome - - 2026-09-29
CVE-2026-102310 Chrome 154前支付缺失授权漏洞 — Chrome - - 2026-09-29
CVE-2026-95342 Chrome 154.0.8037.57 之前 V8 缺失授权致绕过来源策略 — Chrome - - 2026-09-29

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