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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

7192 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-90768 CAPEv2 through commit 471ee4b REST API Task Endpoints Missing Ownership Check — CAPEv2 8.1 High 2026-09-13
CVE-2026-90508 Chengdu Qilu Technology Ludashi Message Dispatch ProtectFilter64.sys MessageNotifyCallback authorization — Ludashi 3.4 Low 2026-09-13
CVE-2026-90551 WWBN AVideo Missing Authorization via video_from_program API — AVideo 5.3 Medium 2026-09-12
CVE-2026-90547 WWBN AVideo Missing Authorization via getBookmarks.json.php — AVideo 5.3 Medium 2026-09-12
CVE-2026-90546 WWBN AVideo Missing Authorization via like.json.php — AVideo 4.3 Medium 2026-09-12
CVE-2026-90545 WWBN AVideo Missing Authorization via commentAddNew.json.php — AVideo 4.3 Medium 2026-09-12
CVE-2026-90544 WWBN AVideo Missing Authorization via videoAddViewCount.json.php — AVideo 4.3 Medium 2026-09-12
CVE-2026-90540 WWBN AVideo Missing Authorization via playListAddVideo.json.php — AVideo 4.3 Medium 2026-09-12
CVE-2026-90537 WWBN AVideo Scheduler sendEmail Missing Authorization via Token — AVideo 8.2 High 2026-09-12
CVE-2026-90535 Flowise before 3.1.4 Denial of Service via text-to-speech/abort — Flowise 6.3 Medium 2026-09-12
CVE-2026-90533 Flowise before 3.1.4 Broken Access Control via organizationuser — Flowise 6.0 Medium 2026-09-12
CVE-2026-11355 DT LMS <= 1.1 - Missing Authorization to Unauthenticated Arbitrary Plugin Settings Modification via Multiple AJAX Actions — DT LMS – elearning, WordPress LMS Plugin 5.3 Medium 2026-09-12
CVE-2026-90454 Zeroc-ice读模式漏配允许修改会话标签 — Malcolm 5.3 Medium 2026-09-11
CVE-2026-90448 只读模式未限制写操作,致记录可被覆盖 — Malcolm 7.1 High 2026-09-11
CVE-2026-49439 OpenRemote read-only asset users can write predicted datapoints — openremote 4.3 Medium 2026-09-11
CVE-2026-68535 Concrete CMS 9.2.0 to 9.5.2 is vulnerable to Missing authorization in the Concrete CMS Area REST API block-create path letting an editor reference files outside their file-manager permissions — Concrete CMS 5.1 Medium 2026-09-11
CVE-2026-81916 Incorrect Authorization in the Concrete CMS Express Entries Dashboard below version 9.5.3 Allows Entry Creation in an Unauthorized Object — Concrete CMS 5.1 Medium 2026-09-11
CVE-2026-81915 In Concrete CMS below 9.5.3, Page Type update omits object-level authorization — Concrete CMS 5.1 Medium 2026-09-11
CVE-2026-62089 WordPress Master Addons for Elementor plugin <= 3.2.2 - Broken Access Control vulnerability — Master Addons for Elementor 7.1 High 2026-09-11
CVE-2026-62137 WordPress bbPress plugin <= 2.6.14 - Sensitive Data Exposure vulnerability — bbPress 5.3 Medium 2026-09-11
CVE-2026-62136 WordPress Flexible Quantity – Measurement Price Calculator for WooCommerce plugin <= 2.3.21 - Broken Access Control vulnerability — Flexible Quantity – Measurement Price Calculator for WooCommerce 5.3 Medium 2026-09-11
CVE-2026-62135 WordPress Booktics plugin <= 1.0.24 - Broken Access Control vulnerability — Booktics 5.3 Medium 2026-09-11
CVE-2026-62132 WordPress Masteriyo - LMS plugin <= 3.4.0 - Broken Access Control vulnerability — Masteriyo - LMS 5.3 Medium 2026-09-11
CVE-2026-62114 WordPress Passster plugin <= 4.3.13 - Broken Access Control vulnerability — Passster 5.3 Medium 2026-09-11
CVE-2026-27378 WordPress Deposits and Partial Payments for WooCommerce plugin <= 3.1.0 - Broken Access Control vulnerability — Deposits and Partial Payments for WooCommerce 5.3 Medium 2026-09-11
CVE-2026-81909 Concrete CMS 9 through 9.5.2 is vulnerable to Missing Authorization in the orphaned-block alias route, allowing an authenticated editor to disclose and force-delete arbitrary blocks — Concrete CMS 5.9 Medium 2026-09-11
CVE-2026-18122 Concrete CMS 9.2.0 to 9.5.2 Express REST API list endpoint exposes restricted Express entries via Missing Authorization — Concrete CMS 6.0 Medium 2026-09-11
CVE-2026-81908 Missing Authorization in Concrete CMS 9.2.0 to 9.5.2 REST API Groups List Endpoint Allows Authenticated Users to Enumerate All Groups — Concrete CMS 6.0 Medium 2026-09-11
CVE-2026-72709 SPIP < 4.4.18 Missing Authorization via ecrire/action/ editer_auteur — SPIP 9.8 Critical 2026-09-11
CVE-2026-8304 Information Disclosure in TUBITAK BILGEM's Pardus About — Pardus About 5.5 Medium 2026-09-11

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