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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8300 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-104070 SPIP Crayons Plugin < 3.5.0 Authorization Bypass RCE — SPIP Crayons Plugin 9.8 Critical 2026-10-06
CVE-2026-105852 Payload relationship-query authorization bypass — payload 6.9 Medium 2026-10-06
CVE-2026-105806 Payload: Improper access control for MCP API keys — payload 8.6 High 2026-10-06
CVE-2026-63691 Dell Container Storage Modules <1.18.0 鉴权缺失漏洞 — Container Storage Modules 6.1 Medium 2026-10-06
CVE-2026-106041 Mooncake Store through 0.3.13.post1 Missing Authorization via NotifyOffloadSuccess RPC — Mooncake 6.5 Medium 2026-10-06
CVE-2026-106040 Mooncake Store through 0.3.13.post1 Missing Authorization via EvictDiskReplica RPC — Mooncake 8.2 High 2026-10-06
CVE-2026-106039 Mooncake Store through 0.3.13.post1 Missing Authorization in Replication Task RPC — Mooncake 6.5 Medium 2026-10-06
CVE-2026-105059 WordPress Delete All Comments of wordpress plugin <= 7.1 - Broken Access Control vulnerability — Delete All Comments of wordpress 6.5 Medium 2026-10-06
CVE-2026-104406 WordPress picu plugin <= 3.10.1 - Broken Access Control vulnerability — picu 7.3 High 2026-10-06
CVE-2026-104387 WordPress PowerPress Podcasting plugin <= 11.17.9 - Broken Access Control vulnerability — PowerPress Podcasting 7.2 High 2026-10-06
CVE-2026-102915 WordPress WPO365 plugin <= 44.1 - Broken Access Control vulnerability — WPO365 8.5 High 2026-10-06
CVE-2026-95526 WordPress BEAR plugin <= 1.2.2 - Broken Access Control vulnerability — BEAR 7.3 High 2026-10-06
CVE-2026-62072 WordPress Progress Planner plugin <= 1.10.0 - Broken Access Control vulnerability — Progress Planner 8.8 High 2026-10-06
CVE-2026-48199 WordPress Sermon'e plugin <= 1.0.2 - Broken Access Control vulnerability — Sermon'e 7.5 High 2026-10-06
CVE-2026-42638 WordPress Easy Digital Downloads plugin <= 3.7.1 - Broken Access Control vulnerability — Easy Digital Downloads 7.5 High 2026-10-06
CVE-2026-42637 WordPress PayPlug for WooCommerce (Official) plugin <= 3.1.0 - Settings Change vulnerability — PayPlug for WooCommerce (Official) 6.5 Medium 2026-10-06
CVE-2026-41560 WordPress WXD Backup Lite plugin <= 1.0.2 - Broken Access Control vulnerability — WXD Backup Lite 7.5 High 2026-10-06
CVE-2026-39798 WordPress TrueBooker plugin <= 1.2.9 - Settings Change vulnerability — TrueBooker 6.5 Medium 2026-10-06
CVE-2026-39796 WordPress Advanced Posts Listing – Show Post List Easily plugin <= 1.0.8 - Broken Access Control vulnerability — Advanced Posts Listing – Show Post List Easily 7.5 High 2026-10-06
CVE-2026-39794 WordPress WooCommerce Multivendor Marketplace – REST API plugin <= 1.6.3 - Broken Access Control vulnerability — WooCommerce Multivendor Marketplace – REST API 7.5 High 2026-10-06
CVE-2026-39787 WordPress 10Web Social Photo Feed plugin <= 1.4.35 - Broken Access Control vulnerability — 10Web Social Photo Feed 6.5 Medium 2026-10-06
CVE-2026-39762 WordPress Autoship Cloud for WooCommerce Subscription Products plugin <= 2.17.1 - Broken Access Control vulnerability — Autoship Cloud for WooCommerce Subscription Products 6.5 Medium 2026-10-06
CVE-2026-39751 WordPress PayPlug for WooCommerce (Official) plugin <= 3.1.0 - Broken Access Control vulnerability — PayPlug for WooCommerce (Official) 7.5 High 2026-10-06
CVE-2026-39749 WordPress App for Cloudflare® plugin <= 1.10.1 - Broken Access Control vulnerability — App for Cloudflare® 6.5 Medium 2026-10-06
CVE-2026-39730 WordPress Wise Chat plugin <= 3.4.3 - Broken Access Control vulnerability — Wise Chat 7.1 High 2026-10-06
CVE-2026-32578 WordPress ECPay Ecommerce for WooCommerce plugin <= 1.1.2606090 - Broken Access Control vulnerability — ECPay Ecommerce for WooCommerce 7.1 High 2026-10-06
CVE-2026-25433 WordPress WP2LEADS plugin <= 3.5.7 - Broken Access Control vulnerability — WP2LEADS 7.1 High 2026-10-06
CVE-2026-25267 Missing Authorization in Core — Snapdragon 7.8 High 2026-10-06
CVE-2026-39789 WordPress Fluent Affiliate Pro plugin <= 1.6.4 - Broken Access Control vulnerability — Fluent Affiliate Pro 7.5 High 2026-10-06
CVE-2026-39599 WordPress WDS MCP Content Manager plugin <= 3.10.4 - Broken Access Control vulnerability — WDS MCP Content Manager 4.3 Medium 2026-10-06

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