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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

7017 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-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
CVE-2026-84757 WordPress WP Compress plugin <= 7.21.28 - Settings Change vulnerability — WP Compress 8.2 High 2026-09-03
CVE-2026-84755 WordPress Mail Mint plugin <= 1.31.0 - Broken Access Control vulnerability — Mail Mint 6.5 Medium 2026-09-03
CVE-2026-84754 WordPress WPFunnels plugin <= 3.12.13 - Broken Access Control vulnerability — WPFunnels 6.5 Medium 2026-09-03
CVE-2026-84238 WordPress YITH Request a Quote for WooCommerce Premium plugin < 4.46.0 - Broken Access Control vulnerability — YITH Request a Quote for WooCommerce Premium 9.8 Critical 2026-09-03
CVE-2026-84215 WordPress Timetics plugin <= 1.0.61 - Broken Access Control vulnerability — Timetics 6.5 Medium 2026-09-03
CVE-2026-55658 Gardens v2: StreamingEscrow buffer drains to the proposal beneficiary on cancel via the permissionless claim() — gardens-v2 7.7 High 2026-09-03
CVE-2026-84989 ntopng's Missing Authorization in REST API Allows Non-Admin Users to Delete and Rename Arbitrary Tags — ntopng 7.1 High 2026-09-03
CVE-2026-85226 MISP OnDemand Correlation Engine Missing Access Control Allows Disclosure of Restricted Correlations — misp 5.3 Medium 2026-09-03
CVE-2026-85213 Kill Bill through 0.24.21 Missing Authorization on AdminResource Endpoints — killbill 7.6 High 2026-09-03
CVE-2026-85212 CRMEB through 6.0.0 Missing Authorization via Inert verifyAuth Role Check — CRMEB 8.3 High 2026-09-03
CVE-2026-85210 Oppia through 3.5.2 Missing Authorization on AdminRoleHandler GET — oppia 4.3 Medium 2026-09-03
CVE-2026-78069 Joomla Extension - j2commerce.com - Missing authorization on Apps controller delegation chain in J2Store 1.0.0-3.3.21, 4.0.0-4.0.21, 4.1.0-4.1.6 — J2Store extension for Joomla 9.5 Critical 2026-09-03
CVE-2026-53635 Open edX Platform: Insufficient Permission on set_course_mode_price() — openedx-platform 7.6 High 2026-09-02
CVE-2026-45730 Nuclio: Missing authorization on project write paths allows any authenticated user to modify or delete any project — nuclio 8.3 High 2026-09-02
CVE-2026-18058 Motorola Smart Connect Application 授权问题漏洞 — Smart Connect Application 7.5 High 2026-09-02
CVE-2026-78601 Missing Authorization in Kibana Leading to Unauthorized Elasticsearch Index Data Exposure — Kibana 5.5 Medium 2026-09-02
CVE-2026-81269 Data field - Moderately critical - Information disclosure - SA-CONTRIB-2026-108 — Data field - - 2026-09-02
CVE-2026-81166 Digital Signage Framework - Moderately critical - Access bypass - SA-CONTRIB-2026-109 — Digital Signage Framework - - 2026-09-02
CVE-2026-81164 Entity PDF - Moderately critical - Access bypass - SA-CONTRIB-2026-114 — Entity PDF - - 2026-09-02
CVE-2026-84217 WordPress Classified Listing plugin <= 6.1.1 - Broken Access Control vulnerability — Classified Listing 5.4 Medium 2026-09-02
CVE-2026-84835 WordPress Rentsyst plugin <= 2.1.2 - Broken Access Control vulnerability — Rentsyst 5.3 Medium 2026-09-02
CVE-2026-84760 WordPress Ultimate Gift Cards For WooCommerce plugin <= 3.2.9 - Broken Access Control vulnerability — Ultimate Gift Cards For WooCommerce 5.3 Medium 2026-09-02
CVE-2026-82223 WordPress WP Event SOlution plugin <= 4.1.22 - Broken Access Control vulnerability — WP Event SOlution 6.5 Medium 2026-09-02
CVE-2026-84805 Kimai 2.61.0 before 2.63.0 Authentication Bypass via API — kimai 4.3 Medium 2026-09-02
CVE-2026-84802 Craft CMS 5.7.0 before 5.10.12 Information Disclosure via AssetsController — cms 4.3 Medium 2026-09-02
CVE-2026-84801 Craft CMS 5.0.0-RC1 before 5.10.11 Authentication Bypass via administrateUsers — cms 8.8 High 2026-09-02
CVE-2026-84800 Craft CMS 5.0.0-RC1 before 5.10.11 File Overwrite via assets/replace-file — cms 7.1 High 2026-09-02

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