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-45766 WordPress Poll Maker plugin <= 4.7.1 - Broken Access Control vulnerability — Poll Maker 5.3 Medium 2025-01-02
CVE-2023-45765 WordPress WP ERP plugin <= 1.12.6 - Broken Access Control vulnerability — WP ERP 4.3 Medium 2025-01-02
CVE-2023-45760 WordPress wpDiscuz plugin <= 7.6.3 - Broken Access Control vulnerability — wpDiscuz 4.3 Medium 2025-01-02
CVE-2023-45636 WordPress Backup & Migration plugin <= 1.4.1 - Broken Access Control vulnerability — WordPress Backup & Migration 5.4 Medium 2025-01-02
CVE-2023-45649 WordPress Appointment Hour Booking plugin <= 1.4.23 - Broken Access Control vulnerability — Appointment Hour Booking 5.3 Medium 2025-01-02
CVE-2023-45275 WordPress Contact Form builder with drag & drop plugin <= 2.3.28 - Broken Access Control vulnerability — Kali Forms 6.5 Medium 2025-01-02
CVE-2023-45631 WordPress Gallery – Image and Video Gallery with Thumbnails plugin <= 2.0.3 - Broken Access Control vulnerability — Responsive Image Gallery, Gallery Album 4.3 Medium 2025-01-02
CVE-2023-45271 WordPress ProductX – Gutenberg WooCommerce Blocks plugin <= 2.7.8 - Broken Access Control vulnerability — WowStore 4.3 Medium 2025-01-02
CVE-2023-45104 WordPress BetterLinks plugin <= 1.6.0 - Broken Access Control vulnerability — BetterLinks 7.3 High 2025-01-02
CVE-2023-45110 WordPress Bold Timeline Lite plugin <= 1.1.9 - Broken Access Control vulnerability — Bold Timeline Lite 4.3 Medium 2025-01-02
CVE-2023-45061 WordPress WP Job Openings plugin <= 3.4.1 - Broken Access Control vulnerability — WP Job Openings 5.3 Medium 2025-01-02
CVE-2023-45101 WordPress Customer Reviews for WooCommerce plugin <= 5.36.0 - Broken Access Control vulnerability — Customer Reviews for WooCommerce 4.3 Medium 2025-01-02
CVE-2023-45045 WordPress WP Custom Widget area plugin <= 1.2.5 - Broken Access Control vulnerability — WP Custom Widget area 5.4 Medium 2025-01-02
CVE-2023-44988 WordPress WP Custom Admin Interface plugin <= 7.32 - Broken Access Control vulnerability — WP Custom Admin Interface 4.3 Medium 2025-01-02
CVE-2023-45002 WordPress WP User Frontend plugin <= 3.6.8 - Broken Access Control vulnerability — WP User Frontend 4.3 Medium 2025-01-02
CVE-2023-44258 WordPress Schema App Structured Data plugin <= 1.23.1 - Broken Access Control + CSRF vulnerability — Schema App Structured Data 5.3 Medium 2025-01-02
CVE-2024-49686 WordPress Landing Page Cat plugin <= 1.7.4 - Broken Access Control vulnerability — Landing Page Cat 5.4 Medium 2024-12-31
CVE-2024-49687 WordPress Smart Manager plugin <= 8.45.0 - Broken Access Control vulnerability — Smart Manager 4.3 Medium 2024-12-31
CVE-2024-49694 WordPress My Wp Brand – Hide menu & Hide Plugin plugin <= 1.1.2 - Broken Access Control vulnerability — My Wp Brand 5.3 Medium 2024-12-31
CVE-2024-49698 WordPress Great Restaurant Menu WP plugin <= 1.4.2 - Broken Access Control vulnerability — Best Restaurant Menu by PriceListo 4.3 Medium 2024-12-31
CVE-2024-51667 WordPress paytium plugin <= 4.4.10 - Broken Access Control vulnerability — Paytium 4.3 Medium 2024-12-31
CVE-2024-55995 WordPress Torod plugin <= 1.7 - Settings Change vulnerability — Torod 6.5 Medium 2024-12-31
CVE-2024-56002 WordPress Contact Form, Survey & Form Builder – MightyForms plugin <= 1.3.9 - Broken Access Control vulnerability — Contact Form, Survey & Form Builder – MightyForms 6.4 Medium 2024-12-31
CVE-2024-56070 WordPress WP SuperBackup plugin <= 2.3.3 - Multiple Subscriber+ Broken Access Control vulnerabilities — WP SuperBackup 7.4 High 2024-12-31
CVE-2024-56066 WordPress Agency Toolkit plugin <= 1.0.23 - Privilege Escalation vulnerability — Agency Toolkit 9.8 Critical 2024-12-31
CVE-2024-56061 WordPress RepairBuddy plugin <= 3.8119 - Account Takeover vulnerability — RepairBuddy 8.8 High 2024-12-31
CVE-2024-55991 WordPress CRM Plugin – WP-CRM System plugin <= 3.2.9.1 - Broken Access Control vulnerability — WP-CRM System 6.5 Medium 2024-12-31
CVE-2024-56031 WordPress Smart Shopify Product plugin <= 1.0.2 - Arbitrary Content Deletion vulnerability — Smart Shopify Product 6.5 Medium 2024-12-31
CVE-2024-56067 WordPress WP SuperBackup plugin <= 2.3.3 - Unauthenticated Backup File Download Vulnerability — WP SuperBackup 7.5 High 2024-12-31
CVE-2023-48775 WordPress WP CleanFix plugin <= 5.6.2 - Broken Access Control vulnerability — WP Cleanfix 5.3 Medium 2024-12-31

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