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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

5953 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-2024-35665 WordPress Insert Post Ads plugin <= 1.3.2 - Broken Access Control vulnerability — Insert Post Ads 5.3 Medium2024-06-11
CVE-2024-35667 WordPress Shopping Cart & eCommerce Store plugin <= 5.5.19 - Broken Access Control vulnerability — WP EasyCart 5.3 Medium2024-06-11
CVE-2024-35671 WordPress MJ Update History plugin <= 1.0.4 - Broken Access Control vulnerability — MJ Update History 4.3 Medium2024-06-11
CVE-2024-35683 WordPress Leyka plugin <= 3.31.1 - Broken Access Control vulnerability — Leyka 5.3 Medium2024-06-11
CVE-2023-52183 WordPress WordPress Backup & Migration plugin <= 1.4.3 - Broken Access Control vulnerability — WordPress Backup & Migration 5.4 Medium2024-06-11
CVE-2024-34442 WordPress weDocs plugin <= 2.1.4 - Broken Access Control vulnerability — weDocs 5.3 Medium2024-06-11
CVE-2024-35685 WordPress Radcliffe 2 theme <= 2.0.17 - Broken Access Control vulnerability — Radcliffe 2 5.3 Medium2024-06-11
CVE-2023-52179 WordPress Product Expiry for WooCommerce plugin <= 2.5 - Broken Access Control vulnerability — Product Expiry for WooCommerce 5.4 Medium2024-06-11
CVE-2024-34813 WordPress WooCommerce Wishlist plugin <= 1.7.8 - Broken Access Control vulnerability — MC Woocommerce Wishlist 5.3 Medium2024-06-11
CVE-2024-34824 WordPress SportsPress – Sports Club & League Manager plugin <= 2.7.20 - Broken Access Control vulnerability — SportsPress – Sports Club & League Manager 4.3 Medium2024-06-11
CVE-2023-52217 WordPress WooCommerce Conversion Tracking plugin <= 2.0.11 - Broken Access Control vulnerability — WooCommerce Conversion Tracking 4.3 Medium2024-06-11
CVE-2024-24704 WordPress Load More Anything plugin <= 3.3.3 - Broken Access Control vulnerability — Load More Anything 5.4 Medium2024-06-11
CVE-2023-52186 WordPress WooCommerce Product Vendors plugin <= 2.2.2 - Unauthenticated Broken Access Control vulnerability — WooCommerce Product Vendors 5.3 Medium2024-06-11
CVE-2024-35692 WordPress GDPR/CCPA Cookie Consent Banner plugin <= 3.2 - Broken Access Control vulnerability — Cookie Consent 5.3 Medium2024-06-11
CVE-2024-35716 WordPress Copymatic plugin <= 1.9 - Broken Access Control vulnerability — Copymatic – AI Content Writer & Generator 6.5 Medium2024-06-11
CVE-2023-33922 WordPress Elementor plugin <= 3.13.2 - Broken Access Control vulnerability — Elementor Website Builder 4.3 Medium2024-06-11
CVE-2023-28775 WordPress Yoast SEO Premium plugin <= 20.4 - Unauthenticated Zapier API Key Reset vulnerability — Yoast SEO Premium 5.3 Medium2024-06-11
CVE-2023-25799 WordPress Tutor LMS plugin <= 2.1.8 - Multiple Broken Access Control vulnerabilities — Tutor LMS 8.3 High2024-06-11
CVE-2024-4319 Advanced Contact form 7 DB <= 2.0.2 - Missing Authorization to Unauthenticated Information Disclosure — Advanced Contact form 7 DB 5.3 Medium2024-06-11
CVE-2024-34691 Missing Authorization check in SAP S/4HANA (Manage Incoming Payment Files) — SAP S/4HANA (Manage Incoming Payment Files) 6.5 Medium2024-06-11
CVE-2024-34690 Missing Authorization check in SAP Student Life Cycle Management (SLcM) — SAP Student Life Cycle Management 5.4 Medium2024-06-11
CVE-2024-37176 Missing Authorization check in SAP BW/4HANA Transformation and DTP — SAP BW/4HANA Transformation and Data Transfer Process 5.5 Medium2024-06-11
CVE-2023-6748 Custom Field Template <= 2.6.1 - Authenticated(Contributor+) Information Exposure — Custom Field Template 4.3 Medium2024-06-11
CVE-2024-34800 WordPress Crafthemes Demo Import plugin <= 3.3 - Arbitrary plugin Installation vulnerability — Crafthemes Demo Import 7.6 High2024-06-10
CVE-2024-4744 WordPress iPages Flipbook plugin <= 1.5.1 - Broken Access Control vulnerability — iPages Flipbook 5.3 Medium2024-06-10
CVE-2024-4745 WordPress Giveaways and Contests by RafflePress plugin <= 1.12.4 - Broken Access Control vulnerability — Giveaways and Contests by RafflePress 4.3 Medium2024-06-10
CVE-2024-22296 WordPress 12 Step Meeting List plugin <= 3.14.28 - Broken Access Control vulnerability — 12 Step Meeting List 4.3 Medium2024-06-10
CVE-2024-22298 WordPress Amelia plugin <= 1.0.98 - Broken Access Control vulnerability — Amelia 5.3 Medium2024-06-10
CVE-2024-21751 WordPress RabbitLoader plugin <= 2.19.13 - Broken Access Control vulnerability — RabbitLoader 5.4 Medium2024-06-10
CVE-2024-23524 WordPress PilotPress plugin <= 2.0.30 - Broken Access Control vulnerability — PilotPress 5.3 Medium2024-06-10

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