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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6890 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-2023-25969 WordPress Contact Form & Lead Form Elementor Builder plugin <= 1.8.4 - Broken Access Control vulnerability — Contact Form & Lead Form Elementor Builder 5.4 Medium 2026-06-11
CVE-2022-45813 WordPress Advanced AJAX Product Filters plugin <= 1.6.3.3 - Broken Access Control + CSRF — Advanced AJAX Product Filters 5.4 Medium 2026-06-11
CVE-2026-4764 Privilege Escalation in Dialogflow CX via Playbook Import — Dialogflow CX - - 2026-06-11
CVE-2022-42479 WordPress Soledad premium theme <= 8.2.5 - Broken Access Control vulnerability — Soledad 5.4 Medium 2026-06-11
CVE-2026-46645 SQLAdmin: Authorization Bypass on `ajax_lookup` — sqladmin 4.3 Medium 2026-06-10
CVE-2026-0272 PAN-OS: Privilege Escalation (PE) Vulnerability in the Command Line Interface (CLI) — Cloud NGFW 5.6 Medium 2026-06-10
CVE-2026-53634 Sharp: Missing Authorization Check in Quick Creation Command Endpoints — sharp 4.3 Medium 2026-06-10
CVE-2026-45549 Roxy-WI: Authorization bypass on POST /smon/agent/action/<action> — guest can stop or restart smon-agent on any host — roxy-wi 8.5 High 2026-06-10
CVE-2026-26237 QuMagie — QuMagie - - 2026-06-10
CVE-2026-47281 Visual Studio Code Elevation of Privilege Vulnerability — Visual Studio Code 9.6 Critical 2026-06-09
CVE-2026-49956 Hermes WebUI < 0.51.269 Profile Isolation Bypass via sessions search — hermes-webui 6.5 Medium 2026-06-09
CVE-2026-49948 Mem0 0.2.8 Missing Authorization via POST /configure Endpoint — mem0 8.1 High 2026-06-09
CVE-2026-49741 TYPO3 CMS - Privilege Escalation & SQL Injection in Form Framework — TYPO3 CMS - - 2026-06-09
CVE-2026-47352 TYPO3 CMS - Broken Access Control in Backend API — TYPO3 CMS - - 2026-06-09
CVE-2026-47351 TYPO3 CMS - Broken Access Control in Clipboard — TYPO3 CMS - - 2026-06-09
CVE-2026-47350 TYPO3 CMS - Broken Access Control in DataHandler — TYPO3 CMS - - 2026-06-09
CVE-2026-47349 TYPO3 CMS - Broken Access Control in Recycler — TYPO3 CMS - - 2026-06-09
CVE-2026-47343 TYPO3 CMS - Destructive Actions on File Mount Folders — TYPO3 CMS - - 2026-06-09
CVE-2026-11607 TYPO3 CMS - Broken Access Control in Form Framework — TYPO3 CMS - - 2026-06-09
CVE-2026-4058 User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration <= 4.3.2 - Missing Authorization to Authenticated (Subscriber+) Subscription Pack Cancellation — User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration 4.3 Medium 2026-06-09
CVE-2026-26236 QuMagie — QuMagie - - 2026-06-09
CVE-2026-44754 Missing caller identification check-in for ODP Data Replication APIs — ODP Data Replication APIs 6.6 Medium 2026-06-09
CVE-2026-44751 Missing Authorization check in Application Server ABAP of SAP NetWeaver and ABAP Platform — SAP NetWeaver AS ABAP and ABAP Platform 7.1 High 2026-06-09
CVE-2026-44750 Missing Authorization check in SAP MDG (Review Match Groups Application) — SAP MDG (Review Match Groups Application) 4.3 Medium 2026-06-09
CVE-2026-10787 Devolutions Server 安全漏洞 — Server - - 2026-06-08
CVE-2026-39910 STACKIT IaaS API Privilege Escalation via Service Account Attachment — IaaS API 8.8 High 2026-06-08
CVE-2026-46444 Flowise: Vector Store No Permission Checks — Flowise - - 2026-06-08
CVE-2026-7624 SEO Plugin by Squirrly SEO <= 12.4.16 - Missing Authorization to Authenticated (Contributor+) Privileged Cloud API Operations — SEO Plugin by Squirrly SEO 4.3 Medium 2026-06-06
CVE-2026-8502 LearnPress <= 4.3.6 - Unauthenticated Sensitive Information Exposure via 'c_status' and 'return_type' Parameters — LearnPress – WordPress LMS Plugin for Create and Sell Online Courses 5.3 Medium 2026-06-06
CVE-2026-9008 Page-list <= 6.2 - Missing Authorization to Authenticated (Contributor+) Sensitive Information Disclosure via Shortcode Attributes — Page-list 4.3 Medium 2026-06-06

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