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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6923 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-2023-40678 WordPress Simple URLs plugin <= 117 - Broken Access Control vulnerability — Simple URLs 5.4 Medium 2024-12-13
CVE-2023-40334 WordPress HUSKY plugin <= 1.3.4.2 - Broken Access Control vulnerability — HUSKY 4.3 Medium 2024-12-13
CVE-2023-40670 WordPress ReviewX plugin <= 1.6.17 - Broken Access Control vulnerability — ReviewX 4.3 Medium 2024-12-13
CVE-2023-40331 WordPress Accordion Slider plugin <= 1.9.6 - Broken Access Control vulnerability — Accordion Slider 4.3 Medium 2024-12-13
CVE-2023-40213 WordPress Justified Gallery plugin <= 1.7.3 - Broken Access Control vulnerability — Justified Gallery 4.3 Medium 2024-12-13
CVE-2023-40203 WordPress MailChimp Forms by MailMunch plugin <= 3.1.4 - Broken Access Control — MailChimp Forms by MailMunch 4.3 Medium 2024-12-13
CVE-2023-40011 WordPress Cost Calculator Builder plugin <= 3.1.42 - Broken Access Control vulnerability — Cost Calculator Builder 5.4 Medium 2024-12-13
CVE-2023-40005 WordPress Easy Digital Downloads plugin <= 3.1.5 - Broken Access Control — Easy Digital Downloads 5.3 Medium 2024-12-13
CVE-2023-40003 WordPress WP Project Manager plugin <= 2.6.7 - Broken Access Control vulnerability — WP Project Manager 6.5 Medium 2024-12-13
CVE-2023-40001 WordPress iThemes Sync plugin <= 2.1.13 - Broken Access Control vulnerability — iThemes Sync 4.3 Medium 2024-12-13
CVE-2023-39997 WordPress Popup by Supsystic plugin <= 1.10.19 - Broken Access Control Vulnerability — Popup by Supsystic 5.3 Medium 2024-12-13
CVE-2023-39996 WordPress Accordion and Accordion Slider plugin <= 1.2.4 - Broken Access Control — Accordion and Accordion Slider 5.3 Medium 2024-12-13
CVE-2023-39920 WordPress Redirection for Contact Form 7 plugin <= 2.9.2 - Broken Access Control vulnerability — Redirection for Contact Form 7 7.5 High 2024-12-13
CVE-2023-39995 WordPress Portfolio and Projects plugin <= 1.3.7 - Broken Access Control vulnerability — Portfolio and Projects 4.3 Medium 2024-12-13
CVE-2023-38514 WordPress Social Share Icons & Social Share Buttons plugin <= 3.5.7 - Broken Access Control vulnerability — Social Share Icons & Social Share Buttons 4.3 Medium 2024-12-13
CVE-2023-39305 WordPress Yet Another Stars Rating plugin <= 3.4.3 - Broken Access Control vulnerability — Yet Another Stars Rating 5.3 Medium 2024-12-13
CVE-2023-38480 WordPress Booster Elementor Addons plugin <= 1.4.9 - Broken Access Control vulnerability — Booster Elementor Addons 5.3 Medium 2024-12-13
CVE-2023-38483 WordPress Instant CSS plugin <= 1.1.4 - Broken Access Control vulnerability — Instant CSS 5.4 Medium 2024-12-13
CVE-2023-38477 WordPress QR code MeCard/vCard generator plugin <= 1.6.0 - Broken Access Control vulnerability — QR code MeCard/vCard generator 4.3 Medium 2024-12-13
CVE-2023-38479 WordPress Simple Googlebot Visit plugin <= 1.2.4 - Broken Access Control vulnerability — Simple Googlebot Visit 5.3 Medium 2024-12-13
CVE-2023-38475 WordPress Donations Made Easy – Smart Donations plugin <= 4.0.12 - Broken Access Control vulnerability — Donations Made Easy – Smart Donations 4.3 Medium 2024-12-13
CVE-2023-38385 WordPress Jupiter X Core plugin <= 3.3.0 - Multiple Auth. Broken Access Control vulnerability — JupiterX Core 8.3 High 2024-12-13
CVE-2023-38383 WordPress Language plugin <= 1.2.1 - Broken Access Control vulnerability — Language 5.4 Medium 2024-12-13
CVE-2023-37987 WordPress YourMembership Single Sign On plugin <= 1.1.3 - Broken Access Control vulnerability — YourMembership Single Sign On 6.5 Medium 2024-12-13
CVE-2023-37989 WordPress Easyship WooCommerce Shipping Rates plugin <= 0.9.0 - Broken Access Control vulnerability — Easyship WooCommerce Shipping Rates 5.4 Medium 2024-12-13
CVE-2023-37984 WordPress Quiz And Survey Master plugin <= 8.1.10 - Broken Access Control vulnerability — Quiz And Survey Master 4.3 Medium 2024-12-13
CVE-2023-37969 WordPress Checkout with Zelle on Woocommerce plugin <= 3.1 - Broken Access Control vulnerability — Checkout with Zelle on Woocommerce 5.3 Medium 2024-12-13
CVE-2023-37971 WordPress WooCommerce Product Stock Alert plugin <= 2.0.1 - Broken Access Control vulnerability — WooCommerce Product Stock Alert 6.5 Medium 2024-12-13
CVE-2023-37967 WordPress DirectoryPress plugin <= 3.6.2 - Unauthenticated Broken Access Control Vulnerability — DirectoryPress 6.5 Medium 2024-12-13
CVE-2023-37887 WordPress WPSchoolPress plugin <= 2.2.7 - Broken Access Control vulnerability — WPSchoolPress 6.5 Medium 2024-12-13

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