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-110363 WordPress LearnPress plugin <= 4.4.10 - Broken Access Control vulnerability — LearnPress 5.4 Medium 2026-10-19
CVE-2026-111836 WordPress FluentCommunity plugin <= 2.11.0 - Broken Access Control vulnerability — FluentCommunity 4.3 Medium 2026-10-19
CVE-2026-111839 WordPress Broadcast Live Video plugin <= 7.3.7 - Broken Access Control vulnerability — Broadcast Live Video 5.3 Medium 2026-10-19
CVE-2026-71563 Apache Answer: MCP Answer Retrieval Exposes Content from Non-Public Questions — Apache Answer - - 2026-10-19
CVE-2026-68482 Apache Answer: Improper Authorization in Question Invite User Lookup — Apache Answer - - 2026-10-19
CVE-2026-112178 MISP Proposal ACL Bypass: Incomplete Distribution Level Check in Shadow Attribute Access Control — MISP 7.1 High 2026-10-19
CVE-2026-111439 pg_read_binary_file_blocks 缺少初始用户权限校验,普通用户可读取 relation 文件块 — openGauss-server 4.3 Medium 2026-10-19
CVE-2026-103091 Insecure Default Policy and Unrestricted OIDC Enrollment in Google OSS Agent Mesh (SAM) — SAM 9.3 Critical 2026-10-19
CVE-2026-97859 Gitea API disclosure of private user social graph, keys and stars — Gitea - - 2026-10-18
CVE-2026-109844 Gitea watched repositories API disclosure after access revocation — Gitea - - 2026-10-18
CVE-2026-112000 Vanus 0.8.0 through 0.9.0 Missing Authorization in Gateway Streaming RPCs — vanus 7.6 High 2026-10-18
CVE-2026-110880 WordPress Kit (formerly ConvertKit) plugin <= 3.4.6 - Broken Access Control vulnerability — Kit (formerly ConvertKit) 6.5 Medium 2026-10-18
CVE-2026-110365 WordPress Advanced File Manager plugin <= 5.4.14 - Broken Access Control vulnerability — Advanced File Manager 6.5 Medium 2026-10-18
CVE-2026-111875 David-Crty Databasement Scheduled Restore SaveScheduledRestoreRequest.php authorization — Databasement 4.7 Medium 2026-10-18
CVE-2026-110882 WordPress SMS Alert Order Notifications plugin <= 4.0.1 - Broken Access Control vulnerability — SMS Alert Order Notifications 4.3 Medium 2026-10-17
CVE-2026-111916 Admidio before 5.0.16 Information Disclosure via rss/links.php Weblinks Feed — admidio 5.3 Medium 2026-10-17
CVE-2026-111914 Admidio 5.0.11 before 5.0.16 Broken Access Control via inventory_data.php — admidio 6.5 Medium 2026-10-17
CVE-2026-111910 phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta Authorization Bypass via attachment.php Downloads — phpMyFAQ 6.5 Medium 2026-10-17
CVE-2026-111897 phpMyFAQ 4.2.0-alpha before 4.2.0-beta Authorization Bypass in Attachment Administration Endpoints — phpMyFAQ 7.1 High 2026-10-17
CVE-2026-111889 phpMyFAQ 4.1.0 before 4.1.9 and 4.2.0-alpha before 4.2.0-beta Missing Authorization via Admin Dashboard — phpMyFAQ 4.3 Medium 2026-10-17
CVE-2026-107744 LearnPress <= 4.4.10 - Missing Authorization to Authenticated (Subscriber+) Email Address Enumeration via 'search-authors' AJAX Action — LearnPress – WordPress LMS Plugin for Create and Sell Online Courses 6.5 Medium 2026-10-17
CVE-2026-109369 WP Booking System <= 2.1.0.3 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation via 'user_permission' Parameter via Cross-Form Nonce Reuse — WP Booking System – Booking Calendar 6.8 Medium 2026-10-17
CVE-2026-108123 WP Booking System <= 2.1.0.3 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'wpbs_action=email_logs' Action — WP Booking System – Booking Calendar 7.5 High 2026-10-17
CVE-2026-109368 WP Booking System <= 2.1.0.3 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via wpbs_refresh_calendar_editor AJAX action — WP Booking System – Booking Calendar 6.5 Medium 2026-10-17
CVE-2026-107763 Fastcache by Host.it <= 1.7.5 - Missing Authorization to Authenticated (Subscriber+) Arbitrary .htaccess Page-Cache Block Modification via updateSettings() admin_action_update Hook — Fastcache by Host.it 4.3 Medium 2026-10-17
CVE-2026-64862 Frappe HR: Missing Authorization on PWA API Endpoints enables Cross-Employee Data access in HRMS — hrms 6.5 Medium 2026-10-16
CVE-2026-108373 ERPNext: Unauthorised access to financial data due to missing validation — erpnext 6.5 Medium 2026-10-16
CVE-2026-108374 ERPNext: Unauthorised status modification due to missing validation — erpnext 7.7 High 2026-10-16
CVE-2026-111723 LingGuo-Drama through commit 8a6924a Broken Access Control via /admin/v1/admins API — LingGuo-Drama 8.8 High 2026-10-16
CVE-2026-111683 Allegro Ralph through 20260902.1 Missing Authorization in Data Center Rack API — ralph 5.4 Medium 2026-10-16

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