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-36681 WordPress Cryptocurrency Widgets – Price Ticker & Coins List plugin <= 2.6.2 - Broken Access Control vulnerability — Cryptocurrency Widgets – Price Ticker & Coins List 5.3 Medium 2024-12-13
CVE-2023-36680 WordPress Image Regenerate & Select Crop plugin <= 7.1.0 - Broken Access Control vulnerability — Image Regenerate & Select Crop 5.4 Medium 2024-12-13
CVE-2023-36531 WordPress LiquidPoll plugin <= 3.3.68 - Broken Access Control vulnerability — LiquidPoll – Advanced Polls for Creators and Brands 4.3 Medium 2024-12-13
CVE-2023-36528 WordPress kk Star Ratings plugin <= 5.4.3 - Rate Manipulation due to IP Spoofing Vulnerability — kk Star Ratings 5.3 Medium 2024-12-13
CVE-2023-36519 WordPress SW Product Bundles plugin <= 2.0.15 - Broken Access Control vulnerability — SW Product Bundles 5.4 Medium 2024-12-13
CVE-2023-36526 WordPress Duplicate Post Page Menu & Custom Post Type plugin <= 2.4.1 - Broken Access Control vulnerability — Duplicate Post Page Menu & Custom Post Type 5.4 Medium 2024-12-13
CVE-2023-36518 WordPress Post Hit Counter plugin <= 1.3.2 - Broken Access Control — Post Hit Counter 4.3 Medium 2024-12-13
CVE-2023-36510 WordPress ReDi Restaurant Reservation plugin <= 23.0211 - Broken Access Control vulnerability — ReDi Restaurant Reservation 7.3 High 2024-12-13
CVE-2023-36509 WordPress CHP Ads Block Detector plugin <= 3.9.5 - Broken Access Control vulnerability — CHP Ads Block Detector 5.4 Medium 2024-12-13
CVE-2023-36506 WordPress YITH WooCommerce Waitlist plugin <= 2.13.0 - Broken Access Control vulnerability — YITH WooCommerce Waiting List 5.3 Medium 2024-12-13
CVE-2023-35875 WordPress Gutenverse – Gutenberg Blocks – Page Builder for Site Editor plugin <= 1.8.5 - Broken Access Control vulnerability — Gutenverse 5.3 Medium 2024-12-13
CVE-2023-35052 WordPress Directorist plugin <= 7.5.4 - Arbitrary Content Deletion vulnerability — Directorist 4.3 Medium 2024-12-13
CVE-2023-35777 WordPress The Events Calendar plugin <= 6.1.2.2 - Broken Access Control vulnerability — The Events Calendar 5.3 Medium 2024-12-13
CVE-2023-35051 WordPress Contact Forms by Cimatti plugin <= 1.5.7 - Broken Access Control vulnerability — Contact Forms by Cimatti 5.4 Medium 2024-12-13
CVE-2023-35046 WordPress Dynamic Visibility for Elementor plugin <= 5.0.5 - Broken Access Control vulnerability — Dynamic Visibility for Elementor 5.4 Medium 2024-12-13
CVE-2023-35037 WordPress Surfer plugin <= 1.3.2.357 - Broken Access Control vulnerability — Surfer 7.6 High 2024-12-13
CVE-2023-34387 WordPress Constant Contact Forms plugin <= 2.0.3 - Broken Access Control vulnerability — Constant Contact Forms 4.3 Medium 2024-12-13
CVE-2023-34376 WordPress Change WooCommerce Add To Cart Button Text plugin <= 1.3 - Broken Access Control vulnerability — Change WooCommerce Add To Cart Button Text 5.4 Medium 2024-12-13
CVE-2023-34381 WordPress Zippy plugin <= 1.6.2 - Broken Access Control vulnerability — Zippy 5.3 Medium 2024-12-13
CVE-2023-34014 WordPress Grid Plus plugin <= 1.3.2 - Broken Access Control vulnerability — Grid Plus 5.4 Medium 2024-12-13
CVE-2023-34019 WordPress Uncanny Toolkit for LearnDash plugin <= 3.6.4.3 - Broken Access Control vulnerability — Uncanny Toolkit for LearnDash 6.5 Medium 2024-12-13
CVE-2023-34009 WordPress Social Media Share Buttons & Social Sharing Icons plugin <= 2.8.1 - Broken Access Control + CSRF — Social Media & Share Icons 4.3 Medium 2024-12-13
CVE-2023-33998 WordPress Easy Social Icons plugin <= 3.2.5 - Broken Access Control vulnerability — Easy Social Icons 4.3 Medium 2024-12-13
CVE-2023-33996 WordPress Spam protection, AntiSpam, FireWall by CleanTalk plugin <= 6.10 - Broken Access Control vulnerability — Spam protection, AntiSpam, FireWall by CleanTalk 8.8 High 2024-12-13
CVE-2023-33995 WordPress Photo Gallery by 10Web plugin <= 1.8.15 - Broken Access Control vulnerability — Photo Gallery by 10Web 4.3 Medium 2024-12-13
CVE-2023-33994 WordPress Slimstat Analytics plugin <= 5.0.5.1 - Broken Access Control vulnerability — Slimstat Analytics 6.5 Medium 2024-12-13
CVE-2023-33928 WordPress WordPress Backup & Migration plugin <= 1.4.0 - Broken Access Control vulnerability — WordPress Backup & Migration 4.3 Medium 2024-12-13
CVE-2023-33324 WordPress Easy Captcha plugin <= 1.0 - Broken Access Control vulnerability — Easy Captcha 6.5 Medium 2024-12-13
CVE-2023-33215 WordPress Taggbox plugin <= 3.3 - Broken Access Control vulnerability — Taggbox 5.4 Medium 2024-12-13
CVE-2023-32798 WordPress Simple Page Ordering plugin <= 2.5.0 - Broken Access Control vulnerability — Simple Page Ordering 5.3 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.