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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6905 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-2024-43134 WordPress Waitlist Woocommerce plugin <= 2.6 - Broken Access Control vulnerability — Waitlist Woocommerce ( Back in stock notifier ) 4.3 Medium 2024-11-01
CVE-2024-43136 WordPress Sunshine Photo Cart plugin <= 3.2.1 - Broken Access Control vulnerability — Sunshine Photo Cart 4.3 Medium 2024-11-01
CVE-2024-43142 WordPress Tutor LMS plugin <= 2.7.3 - Broken Access Control vulnerability — Tutor LMS 4.3 Medium 2024-11-01
CVE-2024-43143 WordPress Registrations for the Events Calendar plugin <= 2.12.1 - Broken Access Control vulnerability — Registrations for the Events Calendar 6.4 Medium 2024-11-01
CVE-2024-43154 WordPress Advanced Cron Manager – debug & control plugin <= 2.5.9 - Broken Access Control vulnerability — Advanced Cron Manager – debug & control 4.3 Medium 2024-11-01
CVE-2024-43146 WordPress Accelerated Mobile Pages plugin <= 1.0.96.1 - Broken Access Control vulnerability — AMP for WP 6.3 Medium 2024-11-01
CVE-2024-43157 WordPress FormCraft plugin <= 1.2.10 - Broken Access Control vulnerability — FormCraft 4.3 Medium 2024-11-01
CVE-2024-43158 WordPress Masteriyo LMS plugin <= 1.11.4 - Broken Access Control vulnerability — Masteriyo - LMS 7.5 High 2024-11-01
CVE-2024-43159 WordPress Masteriyo LMS plugin <= 1.11.6 - Broken Access Control vulnerability — Masteriyo - LMS 5.3 Medium 2024-11-01
CVE-2024-43162 WordPress Easy Digital Downloads plugin <= 3.2.12 - Broken Access Control vulnerability — Easy Digital Downloads 4.3 Medium 2024-11-01
CVE-2024-43208 WordPress Send Emails with Mandrill plugin <= 1.4.1 - Broken Access Control vulnerability — Send Emails with Mandrill 4.3 Medium 2024-11-01
CVE-2024-43209 WordPress Bitly's WordPress Plugin plugin <= 2.7.2 - Broken Access Control vulnerability — Bitly 6.5 Medium 2024-11-01
CVE-2024-43212 WordPress WpTravelly plugin <= 1.7.7 - Broken Access Control vulnerability — WpTravelly 7.5 High 2024-11-01
CVE-2024-43219 WordPress Persian WooCommerce plugin <= 7.1.6 - Broken Access Control vulnerability — Persian WooCommerce 5.3 Medium 2024-11-01
CVE-2024-43215 WordPress Social Slider Feed plugin <= 2.2.2 - Broken Access Control vulnerability — Social Slider Feed 4.3 Medium 2024-11-01
CVE-2024-43223 WordPress EventPrime plugin <= 4.0.3.2 - Broken Access Control vulnerability — EventPrime 4.3 Medium 2024-11-01
CVE-2024-43235 WordPress Meta Box plugin <= 5.9.10 - Broken Access Control vulnerability — Meta Box – WordPress Custom Fields Framework 7.1 High 2024-11-01
CVE-2024-43229 WordPress WP Search Analytics plugin <= 1.4.9 - Broken Access Control vulnerability — WP Search Analytics 4.3 Medium 2024-11-01
CVE-2024-43253 WordPress Smart Online Order for Clover plugin <= 1.5.6 - Broken Access Control vulnerability — Smart Online Order for Clover 5.3 Medium 2024-11-01
CVE-2024-43254 WordPress Smart Online Order for Clover plugin <= 1.5.6 - Broken Access Control vulnerability — Smart Online Order for Clover 4.3 Medium 2024-11-01
CVE-2024-43260 WordPress Clearfy Cache plugin <= 2.2.4 - Broken Access Control vulnerability — Clearfy Cache 5.4 Medium 2024-11-01
CVE-2024-43268 WordPress Backup and Restore WordPress plugin <= 1.50 - Broken Access Control vulnerability — Backup and Restore WordPress 5.4 Medium 2024-11-01
CVE-2024-43270 WordPress Backup and Restore WordPress plugin <= 1.50 - Unauthenticated Broken Access Control vulnerability — Backup and Restore WordPress 5.3 Medium 2024-11-01
CVE-2024-43274 WordPress JS Help Desk – The Ultimate Help Desk plugin <= 2.8.6 - Broken Access Control vulnerability — JS Help Desk – Best Help Desk & Support Plugin 5.8 Medium 2024-11-01
CVE-2024-43273 WordPress Icegram Collect plugin <= 1.3.14 - Broken Access Control vulnerability — Icegram Collect 5.4 Medium 2024-11-01
CVE-2024-43277 WordPress UsersWP plugin <= 1.2.15 - Broken Access Control vulnerability — UsersWP 5.3 Medium 2024-11-01
CVE-2024-43290 WordPress Atarim plugin <= 4.0.1 - Broken Access Control vulnerability — Atarim 5.3 Medium 2024-11-01
CVE-2024-43285 WordPress Presto Player plugin <= 3.0.2 - Broken Access Control vulnerability — Presto Player 6.3 Medium 2024-11-01
CVE-2024-43293 WordPress Recipe Card Blocks for Gutenberg & Elementor plugin <= 3.3.1 - Broken Access Control vulnerability — Recipe Card Blocks for Gutenberg & Elementor 4.3 Medium 2024-11-01
CVE-2024-43296 WordPress HTML5 Video Player plugin <= 2.5.30 - Broken Access Control vulnerability — Flash & HTML5 Video 4.3 Medium 2024-11-01

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