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-107418 WordPress Booktics plugin <= 1.0.28 - Broken Access Control vulnerability — Booktics 5.4 Medium 2026-10-12
CVE-2026-108475 WordPress Broadcast Live Video plugin <= 7.3.6 - Broken Access Control vulnerability — Broadcast Live Video 4.3 Medium 2026-10-12
CVE-2026-108476 WordPress Paid Videochat Turnkey Site plugin <= 7.5.13 - Broken Access Control vulnerability — Paid Videochat Turnkey Site 5.0 Medium 2026-10-12
CVE-2026-108477 WordPress Booktics plugin <= 1.0.28 - Broken Access Control vulnerability — Booktics 5.3 Medium 2026-10-12
CVE-2026-109356 LibreNMS before 26.9.0 Missing Authorization in Port Purge via PortsController — librenms 4.3 Medium 2026-10-12
CVE-2026-109340 SurrealDB 3.1.0 before 3.3.0 Authorization Bypass via REFERENCE ON DELETE CASCADE — surrealdb 5.4 Medium 2026-10-12
CVE-2026-109333 SurrealDB 3.0.0 before 3.3.0 Cross-Tenant Record Read via RETURN FETCH — surrealdb 6.5 Medium 2026-10-12
CVE-2026-109323 Grav Star Ratings 2.0.1 through 2.0.3 Missing Server-Side vote_access Authorization — grav-plugin-star-ratings 5.3 Medium 2026-10-12
CVE-2026-109319 Grav Guestbook Plugin 0.5.0 and 0.5.1 Missing Authorization and CSRF in Moderation — grav-plugin-guestbook 4.3 Medium 2026-10-12
CVE-2026-109316 Grav Data Manager 1.4.0 through 1.4.5 Unauthenticated File Deletion via Admin — grav-plugin-data-manager 6.5 Medium 2026-10-12
CVE-2026-109306 Craft CMS 5.0.0 before 5.10.14 Missing Authorization via app/switch-to-licensed-edition — cms 5.9 Medium 2026-10-12
CVE-2026-109284 Open WebUI 0.11.0 before 0.11.4 Improper Authorization via Chat Fork Endpoint — open-webui 4.3 Medium 2026-10-12
CVE-2026-109203 LogicalDOC Community Edition through 9.3 Missing Authorization via ConvertPdf Servlet — LogicalDOC Community Edition 6.5 Medium 2026-10-12
CVE-2026-109202 LogicalDOC Community Edition through 9.3 Missing Authorization via zip-export Servlet — LogicalDOC Community Edition 6.5 Medium 2026-10-12
CVE-2026-109201 LogicalDOC Community Edition through 9.3 Missing Authorization in DocumentService — LogicalDOC Community Edition 8.3 High 2026-10-12
CVE-2026-109188 jshERP through 3.6 Missing Authorization in Master Data Add and Import Endpoints — jshERP 4.3 Medium 2026-10-12
CVE-2026-109187 jshERP through 3.6 Information Disclosure via /platformConfig/getInfoByKey — jshERP 6.5 Medium 2026-10-12
CVE-2026-109185 jshERP through 3.6 Privilege Escalation via PUT /user/updateUser — jshERP 8.8 High 2026-10-12
CVE-2026-109183 jshERP through 3.6 Approval Bypass via addDepotHeadAndDetail Status Parameter — jshERP 4.3 Medium 2026-10-12
CVE-2026-109184 jshERP through 3.6 Data Scope Bypass via /account/findAccountInOutList — jshERP 4.3 Medium 2026-10-12
CVE-2026-109179 jshERP through 3.6 Missing Authorization via /log/list and /log/info — jshERP 4.3 Medium 2026-10-12
CVE-2026-109178 jshERP through 3.6 Missing Authorization via /log Audit Endpoints — jshERP 5.4 Medium 2026-10-12
CVE-2026-109173 yshop-crm through 2.1.3 Missing Authorization via invoice check endpoint — yshop-crm 4.3 Medium 2026-10-12
CVE-2026-109172 yshop-crm through 2.1.3 Missing Authorization via contract-receivables check endpoint — yshop-crm 4.3 Medium 2026-10-12
CVE-2026-109171 yshop-crm through 2.1.3 Missing Authorization via /admin-api/crm/contract/check — yshop-crm 4.3 Medium 2026-10-12
CVE-2026-108950 Open Source Social Network (OSSN) through 10.1 Missing Authorization via Album Photo Routes — opensource-socialnetwork 5.3 Medium 2026-10-12
CVE-2026-107423 WordPress WP User Manager plugin <= 2.9.22 - Broken Access Control vulnerability — WP User Manager 4.3 Medium 2026-10-12
CVE-2026-107869 WordPress Flexible Subscriptions plugin <= 1.8.4 - Broken Access Control vulnerability — Flexible Subscriptions 4.3 Medium 2026-10-12
CVE-2026-107863 WordPress Products Restricted Users for WooCommerce plugin <= 0.7 - Broken Access Control vulnerability — Products Restricted Users for WooCommerce 5.3 Medium 2026-10-12
CVE-2026-107432 WordPress Event post plugin <= 6.1.1 - Broken Access Control vulnerability — Event post 5.4 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.