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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

5581 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)
ConfidentialityRead 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.
IntegrityModify 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 ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
AvailabilityDoS: 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 DesignDivide 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 DesignEnsure 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 DesignUse 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 DesignFor 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, InstallationUse 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 IDTitleCVSSSeverityPublished
CVE-2026-39610 WordPress WpXmas-Snow plugin <= 1.1 - Broken Access Control vulnerability — WpXmas-Snow 5.3 Medium2026-04-08
CVE-2026-39612 WordPress KuteShop theme <= 4.2.9 - Arbitrary Shortcode Execution vulnerability — KuteShop 5.3 Medium2026-04-08
CVE-2026-39614 WordPress JW Player for WordPress plugin <= 2.3.6 - Broken Access Control vulnerability — JW Player for WordPress 5.4 Medium2026-04-08
CVE-2026-39606 WordPress BizReview plugin <= 1.5.13 - Broken Access Control vulnerability — BizReview 5.3 Medium2026-04-08
CVE-2026-39607 WordPress Filter Plus plugin <= 1.1.17 - Broken Access Control vulnerability — Filter Plus 5.4 Medium2026-04-08
CVE-2026-39609 WordPress Wava Payment plugin <= 0.3.7 - Broken Access Control vulnerability — Wava Payment 5.3 Medium2026-04-08
CVE-2026-39608 WordPress iPOSpays Gateways WC plugin <= 1.3.7 - Broken Access Control vulnerability — iPOSpays Gateways WC 5.3 Medium2026-04-08
CVE-2026-39605 WordPress Super Custom Login plugin <= 1.1 - Broken Access Control vulnerability — Super Custom Login 5.3 Medium2026-04-08
CVE-2026-39592 WordPress DEPART plugin <= 1.0.7 - Broken Access Control vulnerability — DEPART 4.3 Medium2026-04-08
CVE-2026-39602 WordPress Order Tracking plugin <= 3.4.3 - Broken Access Control vulnerability — Order Tracking 5.3 Medium2026-04-08
CVE-2026-39588 WordPress NM Gift Registry and Wishlist Lite plugin <= 5.13 - Broken Access Control vulnerability — NM Gift Registry and Wishlist Lite 5.3 Medium2026-04-08
CVE-2026-39585 WordPress Booktics plugin <= 1.0.16 - Broken Access Control vulnerability — Booktics 5.3 Medium2026-04-08
CVE-2026-39569 WordPress 12 Step Meeting List plugin <= 3.19.9 - Broken Access Control vulnerability — 12 Step Meeting List 6.5 Medium2026-04-08
CVE-2026-39563 WordPress Share This Image plugin <= 2.12 - Broken Access Control vulnerability — Share This Image 5.3 Medium2026-04-08
CVE-2026-39565 WordPress WpTravelly plugin <= 2.1.7 - Broken Access Control vulnerability — WpTravelly 4.3 Medium2026-04-08
CVE-2026-39562 WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.10 - Broken Access Control vulnerability — Client Invoicing by Sprout Invoices 5.3 Medium2026-04-08
CVE-2026-39561 WordPress Revive.so plugin <= 2.0.7 - Broken Access Control vulnerability — Revive.so 5.3 Medium2026-04-08
CVE-2026-39543 WordPress Tourfic plugin <= 2.21.4 - Broken Access Control vulnerability — Tourfic 5.3 Medium2026-04-08
CVE-2026-39528 WordPress WP Delicious plugin <= 1.9.5 - Broken Access Control vulnerability — WP Delicious 5.3 Medium2026-04-08
CVE-2026-39535 WordPress Display Eventbrite Events plugin <= 6.5.6 - Broken Access Control vulnerability — Display Eventbrite Events 5.3 Medium2026-04-08
CVE-2026-39520 WordPress weDocs plugin <= 2.1.18 - Broken Access Control vulnerability — weDocs 5.3 Medium2026-04-08
CVE-2026-39506 WordPress AI Engine (Pro) plugin < 3.4.2 - Broken Access Control vulnerability — AI Engine (Pro) 4.3 Medium2026-04-08
CVE-2026-39509 WordPress Directorist plugin <= 8.5.10 - Broken Access Control vulnerability — Directorist 5.3 Medium2026-04-08
CVE-2026-39505 WordPress Seriously Simple Podcasting plugin <= 3.14.2 - Broken Access Control vulnerability — Seriously Simple Podcasting 5.3 Medium2026-04-08
CVE-2026-39504 WordPress InstaWP Connect plugin <= 0.1.2.5 - Broken Access Control vulnerability — InstaWP Connect 5.4 Medium2026-04-08
CVE-2026-39501 WordPress FOX plugin <= 1.4.5 - Broken Access Control vulnerability — FOX 5.3 Medium2026-04-08
CVE-2026-39488 WordPress SureCart plugin <= 4.0.2 - Broken Access Control vulnerability — SureCart 6.5 Medium2026-04-08
CVE-2026-39485 WordPress Youtube Embed Plus plugin <= 14.2.4 - Broken Access Control vulnerability — Youtube Embed Plus 4.3 Medium2026-04-08
CVE-2026-39477 WordPress CartFlows plugin <= 2.2.3 - Broken Access Control vulnerability — CartFlows 4.3 Medium2026-04-08
CVE-2026-39476 WordPress User Feedback plugin <= 1.10.1 - Broken Access Control vulnerability — User Feedback 4.3 Medium2026-04-08

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