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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8308 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-76340 Missing Authorization for Reloading Token-Signing Keys through the REST API in Splunk Enterprise — Splunk Enterprise 5.3 Medium 2026-08-19
CVE-2026-76336 Improper Access Control through the REST API in Splunk Enterprise — Splunk Enterprise 7.1 High 2026-08-19
CVE-2026-76322 SPL Injection through Dashboard Studio Search Query Options in Splunk Enterprise — Splunk Enterprise 6.7 Medium 2026-08-19
CVE-2026-76319 Remote Code Execution (RCE) through Federated Search in Splunk Enterprise — Splunk Enterprise 8.8 High 2026-08-19
CVE-2026-76257 Missing Authorization through REST API Endpoints in Splunk Secure Gateway — Splunk Enterprise 6.5 Medium 2026-08-19
CVE-2026-76255 Risky Command Safeguards Bypass through Splunk Web in Splunk Enterprise — Splunk Enterprise 6.4 Medium 2026-08-19
CVE-2026-76251 Missing Authorization through REST API Endpoints in the Splunk App for Splunk Observability Cloud — Splunk Enterprise 7.1 High 2026-08-19
CVE-2026-53547 Termix: Account Takeover via Global Settings Disclosure — Termix 8.8 High 2026-08-19
CVE-2026-18544 Portieris is vulnerable to Image Policy Bypass via Unvalidated ownerReference — Portieris 8.1 High 2026-08-19
CVE-2026-54740 Lemmy: Lower-ranked federated moderator can remove higher-ranked moderators — lemmy 6.5 Medium 2026-08-19
CVE-2026-54741 Lemmy: Blocked users can edit private messages sent before the block — lemmy 5.3 Medium 2026-08-19
CVE-2026-16938 Power System Missing Authorization — Power Systems Firmware 6.9 Medium 2026-08-19
CVE-2026-16930 Power System Missing Authorization — Power Systems Firmware 8.2 High 2026-08-19
CVE-2026-55703 Snipe-IT: Maintenance Record Disclosure via Missing Authorization on GET — snipe-it 4.3 Medium 2026-08-19
CVE-2026-55483 Snipe-IT: Privilege Escalation via Missing admin Permission Check in User Creation — snipe-it 4.9 Medium 2026-08-19
CVE-2026-64852 Grav API Plugin: Missing authorization on API-key generate/revoke lets any admin.login user forge keys for any account — grav-plugin-api 8.7 High 2026-08-19
CVE-2026-62667 Grav API Plugin : API Key 'scopes' Never Enforced - Delegated Least-Privilege Keys Carry Full User ACL — grav-plugin-api 8.1 High 2026-08-19
CVE-2026-62670 Fail-open authorization in grav-plugin-flex-objects admin-next API: api.access user gets full CRUD on permission-less directories (requireFlexPermission missing else-deny) — grav-plugin-flex-objects 6.3 Medium 2026-08-19
CVE-2026-58565 Dell Command Update 授权问题漏洞 — Dell Command Update (DCU) 8.8 High 2026-08-19
CVE-2026-58562 Dell Command Update 授权问题漏洞 — Dell Command Update (DCU) 7.3 High 2026-08-19
CVE-2026-45273 MyBooks: Privilege Escalation via Missing Authorization on Admin Settings Endpoint — talebook 8.7 High 2026-08-19
CVE-2026-76223 ArcadeDB before 26.8.1 Permission Bypass via DEFINE FUNCTION — arcadedb 7.1 High 2026-08-19
CVE-2026-76215 phpMyFAQ before 4.1.7 Missing Authorization via child resources — phpMyFAQ 5.3 Medium 2026-08-19
CVE-2026-76211 phpMyFAQ before 4.1.7 Information Disclosure via Admin API — phpMyFAQ 4.3 Medium 2026-08-19
CVE-2026-76209 phpMyFAQ before v4.1.6 Registration Bypass via API — phpMyFAQ 4.3 Medium 2026-08-19
CVE-2026-73385 WordPress Outranking plugin Options plugin <= 1.1.3 - Broken Access Control vulnerability — Outranking Plugin Options 7.5 High 2026-08-19
CVE-2026-73363 WordPress Taxi Booking Manager for WooCommerce plugin < 2.0.8 - Broken Access Control vulnerability — Taxi Booking Manager for WooCommerce 6.5 Medium 2026-08-19
CVE-2026-73394 WordPress Stitch Express plugin <= 1.9.0 - Broken Access Control vulnerability — Stitch Express 7.5 High 2026-08-19
CVE-2026-66589 WordPress B2BKing plugin <= 5.2.30 - Broken Access Control vulnerability — B2BKing 5.4 Medium 2026-08-18
CVE-2026-12631 Broken access-control denial in k_thread_join/k_thread_abort syscall validation in Zephyr kernel — zephyr 6.5 Medium 2026-08-18

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