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-107746 FunnelKit <= 3.16.0.6 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'order_id' / 'order' POST Parameter — FunnelKit – Funnel Builder Plugin for WooCommerce Checkout 7.5 High 2026-10-16
CVE-2026-110721 NotificationX <= 3.3.3 - Missing Authorization to Unauthenticated Arbitrary Content Injection via 'nx_id' Parameter on /popup-submit REST Route — NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar 5.3 Medium 2026-10-16
CVE-2026-109812 Missing Authorization on Secret Endpoints — AIG-302 Series 6.9 Medium 2026-10-16
CVE-2026-92629 联想百应PC客户端越权执行任意代码漏洞 — Baiying PC Client 7.3 High 2026-10-15
CVE-2026-111353 Peppermint through 0.5.5 Missing Authorization via Time-Tracking and Attachment Upload Endpoints — peppermint 4.3 Medium 2026-10-15
CVE-2026-111350 Papermark through 0.22.0 Missing Authorization in Data Room Viewer Group API — Papermark 5.0 Medium 2026-10-15
CVE-2026-111349 Craftplan through 0.7.5 Missing Authorization via CRM Customer JSON:API and GraphQL — Craftplan 5.3 Medium 2026-10-15
CVE-2026-111343 pig through 4.1.1 Missing Authorization via GET /admin/user/details/{id} — pig 4.3 Medium 2026-10-15
CVE-2026-111277 NivoCart through 2.5.1 Guest Order Invoice Disclosure via account/order/download — nivocart 7.5 High 2026-10-15
CVE-2026-105039 EnergizeLab Station Middleware Admin APIs Missing Role Checks — station-middleware 9.6 Critical 2026-10-15
CVE-2026-111235 OpenNMS REST authorization bypass via non-canonical HTTP method — Meridian 9.1 Critical 2026-10-15
CVE-2026-110362 WordPress PlanetStudio Payment Gateway plugin <= 1.3.3 - Broken Access Control vulnerability — PlanetStudio Payment Gateway 5.3 Medium 2026-10-15
CVE-2026-110374 WordPress Login with phone number plugin <= 1.8.77 - Broken Access Control vulnerability — Login with phone number 4.3 Medium 2026-10-15
CVE-2026-108499 WordPress Knowledge Base plugin <= 3.2.0 - Broken Access Control vulnerability — Knowledge Base 5.3 Medium 2026-10-15
CVE-2026-110364 WordPress Flexible Quantity – Measurement Price Calculator for WooCommerce plugin <= 2.3.23 - Broken Access Control vulnerability — Flexible Quantity – Measurement Price Calculator for WooCommerce 5.3 Medium 2026-10-15
CVE-2026-109689 WordPress Sunshine Photo Cart plugin <= 3.7.4 - Broken Access Control vulnerability — Sunshine Photo Cart 5.3 Medium 2026-10-15
CVE-2026-110360 WordPress Ajax Search Lite plugin <= 4.14.5 - Broken Access Control vulnerability — Ajax Search Lite 5.3 Medium 2026-10-15
CVE-2026-109897 WordPress Strong Testimonials plugin <= 3.3.12 - Broken Access Control vulnerability — Strong Testimonials 5.4 Medium 2026-10-15
CVE-2026-110378 WordPress Ninja Forms Signature Contract Add-On plugin <= 3.2.5 - Broken Access Control vulnerability — Ninja Forms Signature Contract Add-On 5.3 Medium 2026-10-15
CVE-2026-96449 WordPress WP EasyPay plugin <= 4.5.4 - Broken Access Control vulnerability — WP EasyPay 5.3 Medium 2026-10-15
CVE-2026-110888 WordPress AI Engine plugin <= 3.8.3 - Broken Access Control vulnerability — AI Engine 4.3 Medium 2026-10-15
CVE-2026-110891 WordPress WordLift plugin <= 3.54.15 - Broken Access Control vulnerability — WordLift 5.4 Medium 2026-10-15
CVE-2026-110367 WordPress APIExperts Square for WooCommerce plugin <= 4.7.5 - Broken Access Control vulnerability — APIExperts Square for WooCommerce 5.3 Medium 2026-10-15
CVE-2026-110371 WordPress Strong Testimonials plugin <= 3.3.12 - Broken Access Control vulnerability — Strong Testimonials 4.3 Medium 2026-10-15
CVE-2026-55414 NL Portal Backend Libraries: Unauthenticated form resolver forwards the privileged Objecten-API token to a caller-supplied URL (SSRF) — nl-portal-backend-libraries 5.3 Medium 2026-10-15
CVE-2026-97712 Nexus Repository 3 - Privilege Escalation via Role Management — Nexus Repository 3 8.7 High 2026-10-15
CVE-2026-97665 Nexus Repository 3 - Missing Authorization on NuGet Symbol Package Upload — Nexus Repository 3 7.1 High 2026-10-15
CVE-2026-111092 JetBrains YouTrack越权执行命令漏洞 — YouTrack 6.5 Medium 2026-10-15
CVE-2026-75505 EspoCRM: Access control bypass in Mass Update letting regular user with Mass Update permission read any attachment — espocrm 6.0 Medium 2026-10-15
CVE-2026-46691 EspoCRM: IDOR in Import exportErrors Endpoint Leaks CSV Data of Other Users — espocrm 6.5 Medium 2026-10-15

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