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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8304 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-54519 AI Agent Automation: Missing ownership checks in memory APIs allow cross-user memory read and deletion — ai-agent-automation 8.8 High 2026-09-17
CVE-2026-16582 Booking for Appointments and Events Calendar - Amelia <= 2.4.5 - Missing Authorization to Unauthenticated Payment Bypass — Booking for Appointments and Events Calendar – Amelia 5.3 Medium 2026-09-17
CVE-2026-16750 Motors – Car Dealership & Classified Listings <= 1.4.120 - Missing Authorization to Unauthenticated Private/Draft/Password-Protected Listings Exposure — Motors – Car Dealership & Classified Listings Plugin 5.3 Medium 2026-09-17
CVE-2026-14311 Booking for Appointments and Events Calendar – Amelia (Premium) <= 2.4.4 - Authenticated (Custom+) Missing Authorization to Limited Account Takeover — Booking for Appointments and Events Calendar – Amelia 5.4 Medium 2026-09-17
CVE-2026-93378 Chrome 153.0.8010.52前存储缺失授权漏洞 — Chrome - - 2026-09-17
CVE-2026-92992 Dromara mayfly-go AI Assistant ai.go authorization — mayfly-go 6.3 Medium 2026-09-17
CVE-2026-49292 Kiwi TCMS: The /init-db/ page renders and responds to requests after first use — Kiwi - - 2026-09-17
CVE-2026-54676 Scoold: GET /api/posts/{id}/answers leaks private-space replies when personal API tokens are enabled — scoold 6.5 Medium 2026-09-17
CVE-2026-54677 Scoold: Authenticated user can post replies and comments to private-space questions without space membership — scoold 6.5 Medium 2026-09-17
CVE-2026-78528 WordPress BerqWP plugin <= 4.1.15 - Broken Access Control vulnerability — BerqWP 5.3 Medium 2026-09-17
CVE-2026-74017 WordPress User Registration plugin <= 5.2.7 - Broken Access Control vulnerability — User Registration 5.3 Medium 2026-09-17
CVE-2026-74002 WordPress Booking Calendar plugin <= 11.7 - Broken Access Control vulnerability — Booking Calendar 5.3 Medium 2026-09-17
CVE-2026-74000 WordPress Simple Membership plugin <= 4.8.2 - Broken Access Control vulnerability — Simple Membership 5.3 Medium 2026-09-17
CVE-2026-66676 WordPress Easy Invoice plugin <= 2.3.8 - Broken Access Control vulnerability — Easy Invoice 5.3 Medium 2026-09-17
CVE-2026-87831 Checkout Field Manager < 7.9.7 - Subscriber+ Arbitrary Attachment Deletion via Customer Address Custom Field — Checkout Field Manager (Checkout Manager) for WooCommerce 4.3 Medium 2026-09-17
CVE-2026-92589 Craft CMS 5.0.0 before 5.10.13 Broken Access Control via nested-elements/reorder — cms 4.3 Medium 2026-09-16
CVE-2026-92586 AVideo through 29.0 Missing Authorization via comment API endpoint — AVideo 4.3 Medium 2026-09-16
CVE-2026-92585 AVideo through 29.0 Missing Authorization Check via API Like Endpoint — AVideo 4.3 Medium 2026-09-16
CVE-2026-92802 kan through 0.6.0 Authorization Bypass via GitHub Project Import — kan 4.3 Medium 2026-09-16
CVE-2026-92803 LibreTranslate through 1.9.6 Missing Access Check on the download_file Route — LibreTranslate 5.3 Medium 2026-09-16
CVE-2026-92794 OpenSign through 2.41.3 Information Disclosure via getDocument — OpenSign 7.5 High 2026-09-16
CVE-2026-92783 Yeti through 2.11.0 Missing Authorization on RBAC Relationship Deletion — yeti 8.1 High 2026-09-16
CVE-2026-92780 KnowStreaming through 3.4.1 Missing Authorization on the REST API — KnowStreaming 8.8 High 2026-09-16
CVE-2026-92772 Leantime before 3.9.6 Unauthorized Plugin Installation via HTMX — leantime 7.1 High 2026-09-16
CVE-2026-92763 Rundeck through 6.2.1 Authorization Bypass via Project Import — rundeck 8.1 High 2026-09-16
CVE-2026-92762 Pelican Panel before 1.0.0-beta35 Authorization Bypass via Startup — panel 8.8 High 2026-09-16
CVE-2026-92761 WebVirtCloud Missing Authorization on Instance Control Actions — webvirtcloud 8.8 High 2026-09-16
CVE-2026-92754 PatrowlManager through 1.8.4 Improper Access Control via users API — PatrowlManager 4.3 Medium 2026-09-16
CVE-2026-92753 PatrowlManager through 1.8.4 Authorization Bypass via Events API — PatrowlManager 7.1 High 2026-09-16
CVE-2026-92750 Harness through 3.3.0 Missing Access Control via infraproviders endpoint — harness 6.5 Medium 2026-09-16

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