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-53769 Avo: Direct attachment upload endpoint lacks upload authorization and bypasses field-level upload policy — avo 6.5 Medium 2026-09-04
CVE-2026-63464 Nebula-mesh allows non-admin operators to disable webhook SSRF protection via `allow_private` — nebula-mesh 7.7 High 2026-09-04
CVE-2026-53602 nebula-mesh - Host revocation is not durable: blocked/offboarded hosts can regain a valid certificate — nebula-mesh 6.9 Medium 2026-09-04
CVE-2026-78328 SonicWALL Network Security Manager 授权问题漏洞 — Network Security Manager (NSM) - - 2026-09-04
CVE-2026-85669 potpie through 2.0.0 Missing Ownership Check via code-changes sync — potpie 6.5 Medium 2026-09-04
CVE-2026-85651 Trigger.dev before 4.5.2 Unauthorized Environment Access via Run Replay — trigger.dev 8.5 High 2026-09-04
CVE-2026-85605 Slink before 1.12.3 Missing Authorization on Image Comment Endpoints — slink 5.3 Medium 2026-09-04
CVE-2026-19081 Missing Authorization Allows Unauthorized Access to Critical POS Functions in Gastromenum's Gastromenum Ticket and QR Menu System — Gastromenum Ticket and QR Menu System 4.3 Medium 2026-09-04
CVE-2026-19043 Authorization Bypass Critical POS Management Functions in Menulux Software's Menulux Portal — Menulux Portal 4.3 Medium 2026-09-04
CVE-2026-85589 phpMyFAQ before 4.2.0-alpha.2 Missing Authorization via Dashboard API — phpMyFAQ 5.3 Medium 2026-09-04
CVE-2026-85578 SiYuan through 3.8.1 Authorization Bypass via getFile — siyuan 6.5 Medium 2026-09-04
CVE-2026-27347 WordPress JetPopup plugin <= 2.0.20.2 - Broken Access Control vulnerability — JetPopup 5.3 Medium 2026-09-04
CVE-2026-85512 SourceCodester Class and Exam Timetabling System session.php authorization — Class and Exam Timetabling System 7.3 High 2026-09-04
CVE-2026-85533 MISP Sharing Group Authorization Bypass via Omitted Distribution Parameter — misp 7.6 High 2026-09-04
CVE-2026-85311 WordPress MarketKing plugin <= 2.1.60 - Broken Access Control vulnerability — MarketKing 5.3 Medium 2026-09-04
CVE-2026-32480 WordPress WCFM Membership plugin <= 2.11.11 - Broken Access Control vulnerability — WCFM Membership 5.3 Medium 2026-09-04
CVE-2026-67398 WebPros WHMCS 授权问题漏洞 — WHMCS 8.2 High 2026-09-03
CVE-2026-70178 Microsoft Fabric Elevation of Privilege Vulnerability — Microsoft Fabric 8.5 High 2026-09-03
CVE-2026-85433 MOOS essential-moos through 10.0.1 pShare Unauthorized Runtime Route Reconfiguration — essential-moos 9.8 Critical 2026-09-03
CVE-2026-85395 UnoPim before 2.1.3 Missing Authorization on Integration Management Routes — unopim 7.1 High 2026-09-03
CVE-2026-85390 Checkmate through 3.11.0 Missing Authorization on Maintenance Window, Notification, and Check Deletion Routes — Checkmate 7.1 High 2026-09-03
CVE-2026-78596 Missing Authorization in Kibana Leading to Unauthorized Cross-Space Write Operations — Kibana 4.3 Medium 2026-09-03
CVE-2026-78595 Missing Authorization in Kibana Fleet Plugin Leading to Cross-Space Agent Data Disclosure — Kibana 4.3 Medium 2026-09-03
CVE-2026-63219 Unauthenticated file upload via missing authorization on formatter upload endpoint — core-geonetwork 8.6 High 2026-09-03
CVE-2026-85304 WordPress Unlimited Elements For Elementor (Free Widgets, Addons, Templates) plugin <= 2.0.17 - Broken Access Control vulnerability — Unlimited Elements For Elementor (Free Widgets, Addons, Templates) 5.3 Medium 2026-09-03
CVE-2026-85309 WordPress Ultimate Maps by Supsystic plugin <= 1.5.3 - Broken Access Control vulnerability — Ultimate Maps by Supsystic 5.3 Medium 2026-09-03
CVE-2026-85306 WordPress MountDev AI MCP Connector for WordPress plugin <= 1.6.5 - Broken Access Control vulnerability — MountDev AI MCP Connector for WordPress 6.5 Medium 2026-09-03
CVE-2026-84847 WordPress Quick Event Manager plugin <= 9.17 - Broken Access Control vulnerability — Quick Event Manager 7.5 High 2026-09-03
CVE-2026-84779 WordPress Agentimus – AI SEO, llms.txt & MCP for AI Agents plugin <= 1.51.0 - Broken Access Control vulnerability — Agentimus – AI SEO, llms.txt &amp; MCP for AI Agents 8.1 High 2026-09-03
CVE-2026-84758 WordPress Business Directory plugin <= 6.4.26 - Broken Access Control vulnerability — Business Directory 6.5 Medium 2026-09-03

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