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-32408 WordPress Brizy plugin <= 2.7.23 - Broken Access Control vulnerability — Brizy 4.3 Medium2026-03-13
CVE-2026-32407 WordPress WPC Smart Wishlist for WooCommerce plugin <= 5.0.8 - Broken Access Control vulnerability — WPC Smart Wishlist for WooCommerce 4.3 Medium2026-03-13
CVE-2026-32410 WordPress WBW Currency Switcher for WooCommerce plugin <= 2.2.5 - Broken Access Control vulnerability — WBW Currency Switcher for WooCommerce 5.3 Medium2026-03-13
CVE-2026-32402 WordPress Image Slider by Ays plugin <= 2.7.1 - Broken Access Control vulnerability — Image Slider by Ays 5.3 Medium2026-03-13
CVE-2026-32404 WordPress Studio99 WP Monitor plugin <= 1.0.3 - Broken Access Control vulnerability — Studio99 WP Monitor 5.3 Medium2026-03-13
CVE-2026-32406 WordPress WPC Product Bundles for WooCommerce plugin <= 8.4.5 - Broken Access Control vulnerability — WPC Product Bundles for WooCommerce 4.3 Medium2026-03-13
CVE-2026-32397 WordPress Filter & Grids plugin <= 3.5.1 - Broken Access Control vulnerability — Filter & Grids 5.3 Medium2026-03-13
CVE-2026-32394 WordPress PublishPress Capabilities plugin <= 2.31.0 - Broken Access Control vulnerability — PublishPress Capabilities 4.3 Medium2026-03-13
CVE-2026-32396 WordPress Team plugin <= 5.0.13 - Broken Access Control vulnerability — Team 5.3 Medium2026-03-13
CVE-2026-32395 WordPress Xpro Addons For Beaver Builder – Lite plugin <= 1.5.6 - Broken Access Control vulnerability — Xpro Addons For Beaver Builder – Lite 5.3 Medium2026-03-13
CVE-2026-32391 WordPress SmartFix theme < 1.2.4 - Broken Access Control vulnerability — SmartFix 5.4 Medium2026-03-13
CVE-2026-32388 WordPress GLB theme <= 1.2.2 - Broken Access Control vulnerability — GLB 5.4 Medium2026-03-13
CVE-2026-32390 WordPress Nanosoft theme < 1.3.2 - Broken Access Control vulnerability — Nanosoft 5.4 Medium2026-03-13
CVE-2026-32387 WordPress Checkout for PayPal plugin <= 1.0.46 - Broken Access Control vulnerability — Checkout for PayPal 5.3 Medium2026-03-13
CVE-2026-32386 WordPress Envo Extra plugin <= 1.9.13 - Broken Access Control vulnerability — Envo Extra 4.3 Medium2026-03-13
CVE-2026-32385 WordPress RegistrationMagic plugin <= 6.0.7.6 - Broken Access Control vulnerability — RegistrationMagic 5.4 Medium2026-03-13
CVE-2026-32383 WordPress Ridhi theme <= 1.1.2 - Broken Access Control vulnerability — Ridhi 5.3 Medium2026-03-13
CVE-2026-32381 WordPress App Landing Page theme <= 1.2.2 - Broken Access Control vulnerability — App Landing Page 5.3 Medium2026-03-13
CVE-2026-32380 WordPress Numinous theme <= 1.3.0 - Broken Access Control vulnerability — Numinous 5.3 Medium2026-03-13
CVE-2026-32382 WordPress Digital Download theme <= 1.1.4 - Broken Access Control vulnerability — Digital Download 5.3 Medium2026-03-13
CVE-2026-32377 WordPress Pranayama Yoga theme <= 1.2.2 - Broken Access Control vulnerability — Pranayama Yoga 5.3 Medium2026-03-13
CVE-2026-32379 WordPress Rara Academic theme <= 1.2.2 - Broken Access Control vulnerability — Rara Academic 5.3 Medium2026-03-13
CVE-2026-32376 WordPress Kalon theme <= 1.2.9 - Broken Access Control vulnerability — Kalon 5.3 Medium2026-03-13
CVE-2026-32378 WordPress Book Landing Page theme <= 1.2.7 - Broken Access Control vulnerability — Book Landing Page 5.3 Medium2026-03-13
CVE-2026-32375 WordPress Travel Diaries theme <= 1.2.4 - Broken Access Control vulnerability — Travel Diaries 5.3 Medium2026-03-13
CVE-2026-32371 WordPress Elegant Pink theme <= 1.3.3 - Broken Access Control vulnerability — Elegant Pink 5.3 Medium2026-03-13
CVE-2026-32374 WordPress The Minimal theme <= 1.2.9 - Broken Access Control vulnerability — The Minimal 5.3 Medium2026-03-13
CVE-2026-32373 WordPress SMS Alert Order Notifications plugin <= 3.9.0 - Broken Access Control vulnerability — SMS Alert Order Notifications 5.4 Medium2026-03-13
CVE-2026-32370 WordPress Influencer theme <= 1.1.7 - Broken Access Control vulnerability — Influencer 5.3 Medium2026-03-13
CVE-2026-32362 WordPress WP Sessions Time Monitoring Full Automatic plugin <= 1.1.3 - Broken Access Control vulnerability — WP Sessions Time Monitoring Full Automatic 5.3 Medium2026-03-13

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