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-46694 EspoCRM: Portal User ACL Bypass Exposes Internal Stream Notes — espocrm 6.5 Medium 2026-10-15
CVE-2026-109692 WordPress User Registration plugin <= 5.2.8 - Broken Access Control vulnerability — User Registration 7.1 High 2026-10-15
CVE-2026-11905 Elementor Website Builder <= 4.2.3 - Missing Authorization to Authenticated (Contributor+) Sensitive Information Exposure via 'is_public' and 'keys_conversion_map' Parameters — Elementor Website Builder – more than just a page builder 4.3 Medium 2026-10-15
CVE-2026-17031 Checkout Field Manager (Checkout Manager) for WooCommerce <= 7.9.6 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Media Deletion via Checkout File Field Attachment ID — Checkout Field Manager (Checkout Manager) for WooCommerce 8.1 High 2026-10-15
CVE-2026-76066 IntentKit 2.6.3 Executor Tool Authorization Bypass via ToolNode — intentkit 7.5 High 2026-10-15
CVE-2026-107795 Improper Authorization in TP-Link Omada Controller TLS Certificate and Private Key Management API — Omada Software Controller 7.5 High 2026-10-14
CVE-2026-61843 FileRise: Unauthenticated File Overwrite Through Upload-Enabled Folder Shares — FileRise 8.2 High 2026-10-14
CVE-2026-102985 Plane: Any project member can modify (deactivate) other members' records — plane 6.5 Medium 2026-10-14
CVE-2026-110773 GrowChief through 0.3.0 Missing Authorization via /users/all-users Endpoint — growchief 4.3 Medium 2026-10-14
CVE-2026-110772 Sure 0.7.0 through 0.7.6-alpha.6 Missing Authorization via Transaction Bulk Update — sure 4.3 Medium 2026-10-14
CVE-2026-108480 WordPress Skydropx plugin <= 2.1.4 - Broken Access Control vulnerability — Skydropx 8.2 High 2026-10-14
CVE-2026-88164 Microsoft Office SharePoint Elevation of Privilege Vulnerability — Microsoft SharePoint Server Subscription Edition 8.8 High 2026-10-14
CVE-2026-100404 Zulip: Guests can read new messages in non-subscribed public channels — zulip 6.5 Medium 2026-10-14
CVE-2026-91156 Discourse: Chat MessageBus delivers read-restricted messages to unauthorized users — discourse 7.5 High 2026-10-14
CVE-2026-110629 VentureDrake Laravel CRM before 2.4.0 Missing Authorization via Livewire Actions — laravel-crm 6.5 Medium 2026-10-14
CVE-2026-110624 Papermerge Core through 3.5.3 Missing Authorization via /tags/all and /document-types/all — papermerge-core 3.1 Low 2026-10-14
CVE-2026-110623 Papermerge Core through 3.5.3 Missing Authorization in Shared Nodes API — papermerge-core 7.5 High 2026-10-14
CVE-2026-110621 Swetrix Cloud before 5.1.0 Missing Authorization via POST /project/organisation/:orgId — swetrix 8.8 High 2026-10-14
CVE-2026-110622 Papermerge Core through 3.5.3 Missing Authorization in Page Management and OCR Endpoints — papermerge-core 7.5 High 2026-10-14
CVE-2026-110617 we-mp-rss through 1.5.3 Missing Authorization via Export File Download Endpoint — we-mp-rss 4.8 Medium 2026-10-14
CVE-2026-110615 jshERP through 3.6 Missing Authorization via /user/batchSetStatus — jshERP 7.1 High 2026-10-14
CVE-2025-71433 Kaneo before 2.1.6 Missing Authorization Allows Cross-Workspace Data Access — kaneo 7.5 High 2026-10-14
CVE-2026-107417 WordPress Push Notification for Post and BuddyPress plugin <= 3.23 - Broken Access Control vulnerability — Push Notification for Post and BuddyPress 6.5 Medium 2026-10-14
CVE-2026-107426 WordPress Paid Videochat Turnkey Site plugin <= 7.5.12 - Broken Access Control vulnerability — Paid Videochat Turnkey Site 7.3 High 2026-10-14
CVE-2026-82026 Radar < 1.12.2 Missing Authorization via /api/local-terminal — radar 8.8 High 2026-10-14
CVE-2026-107425 WordPress Bus Ticket Booking with Seat Reservation plugin <= 5.9.7 - Broken Access Control vulnerability — Bus Ticket Booking with Seat Reservation 6.5 Medium 2026-10-14
CVE-2026-107433 WordPress WP OAuth Server plugin <= 6.4.0 - Broken Access Control vulnerability — WP OAuth Server 6.5 Medium 2026-10-14
CVE-2026-107431 WordPress JetFormBuilder plugin <= 3.6.6 - Broken Access Control vulnerability — JetFormBuilder 7.5 High 2026-10-14
CVE-2026-103907 Jeg Kit for Elementor <= 3.2.19 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via 'jeg_find_author' AJAX Action — Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress 6.5 Medium 2026-10-14
CVE-2026-110227 WordPress Restricted Site Access plugin <= 7.6.2 - Broken Access Control vulnerability — Restricted Site Access 5.3 Medium 2026-10-14

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