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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6908 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-26520 WordPress Advanced Text Widget plugin <= 2.1.2 - Broken Access Control vulnerability — Advanced Text Widget 5.3 Medium 2024-12-09
CVE-2023-26522 WordPress WP Repost plugin <= 0.1 - Broken Access Control vulnerability — WP Repost 6.5 Medium 2024-12-09
CVE-2023-27428 WordPress WP users media plugin <= 4.2.3 - Broken Access Control vulnerability — WP users media 5.4 Medium 2024-12-09
CVE-2023-27449 WordPress Total Poll Lite plugin <= 4.8.6 - Broken Access Control vulnerability — Total Poll Lite 6.3 Medium 2024-12-09
CVE-2023-27454 WordPress Rife Elementor Extensions & Templates plugin <= 1.1.10 - Broken Access Control vulnerability — Rife Elementor Extensions & Templates 5.4 Medium 2024-12-09
CVE-2023-27625 WordPress Site Reviews plugin <= 6.5.0 - Broken Access Control vulnerability — Site Reviews 4.3 Medium 2024-12-09
CVE-2023-27626 WordPress Stock Ticker plugin <= 3.23.0 - Broken Access Control vulnerability — Stock Ticker 5.3 Medium 2024-12-09
CVE-2023-28168 WordPress WordPress Console plugin <= 0.3.9 - Broken Access Control vulnerability — WordPress Console 3.7 Low 2024-12-09
CVE-2023-28165 WordPress Backup Bank: WordPress Backup Plugin plugin <= 4.0.28 - Broken Access Control vulnerability — Backup Bank: WordPress Backup Plugin 4.3 Medium 2024-12-09
CVE-2023-28416 WordPress Chankhe theme <= 1.0.5 - Authenticated Arbitrary Plugin Activation vulnerability — Chankhe 4.3 Medium 2024-12-09
CVE-2023-28417 WordPress Dynamics 365 Integration plugin <= 1.3.12 - Broken Access Control vulnerability — Dynamics 365 Integration 5.4 Medium 2024-12-09
CVE-2023-28532 WordPress Real Estate Directory theme <= 1.0.5 - Authenticated Arbitrary Plugin Activation — Real Estate Directory 4.3 Medium 2024-12-09
CVE-2023-28536 WordPress Branded Social Images plugin <= 1.1.0 - Broken Access Control vulnerability — Branded Social Images 5.3 Medium 2024-12-09
CVE-2023-28689 WordPress JS Job Manager plugin <= 2.0.0 - Broken Access Control vulnerability — JS Job Manager 6.5 Medium 2024-12-09
CVE-2023-29173 WordPress Product Category Tree plugin <= 2.5 - Broken Access Control vulnerability — Product Category Tree 5.3 Medium 2024-12-09
CVE-2023-29237 WordPress Remove Duplicate Posts plugin <= 1.3.5 - Broken Access Control vulnerability — Remove Duplicate Posts 6.3 Medium 2024-12-09
CVE-2023-29239 WordPress LuckyWP Scripts Control plugin <= 1.2.1 - Broken Access Control vulnerability — LuckyWP Scripts Control 5.4 Medium 2024-12-09
CVE-2023-29429 WordPress User Registration plugin <= 2.3.2.1 - Broken Access Control vulnerability — User Registration 5.3 Medium 2024-12-09
CVE-2023-29422 WordPress Dynamics 365 Integration plugin <= 1.3.13 - Broken Access Control vulnerability — Dynamics 365 Integration 4.3 Medium 2024-12-09
CVE-2023-29431 WordPress qTranslate X Cleanup and WPML Import plugin <= 3.0.1 - Broken Access Control vulnerability — qTranslate X Cleanup and WPML Import 4.3 Medium 2024-12-09
CVE-2023-29433 WordPress tencentcloud-cos plugin <= 1.0.7 - Broken Access Control vulnerability — tencentcloud-cos 5.4 Medium 2024-12-09
CVE-2023-30476 WordPress Blogger Buzz theme <= 1.2.2 - Broken Access Control vulnerability — Blogger Buzz 4.3 Medium 2024-12-09
CVE-2023-30479 WordPress Stamped.io Product Reviews & UGC for WooCommerce plugin <= 2.3.2 - Broken Access Control vulnerability — Stamped.io Product Reviews & UGC for WooCommerce 5.3 Medium 2024-12-09
CVE-2023-30488 WordPress Featured Post Creative plugin <= 1.2.7 - Broken Access Control vulnerability — Featured Post Creative 5.3 Medium 2024-12-09
CVE-2023-30486 WordPress Square theme <= 2.0.0 - Broken Access Control — Square 4.3 Medium 2024-12-09
CVE-2023-30783 WordPress Smart WooCommerce Search plugin <= 2.5.0 - Broken Access Control — Smart WooCommerce Search 4.3 Medium 2024-12-09
CVE-2023-30870 WordPress Sharkdropship for AliExpress Dropship and Affiliate plugin <= 2.2.3 - Multiple Broken Access Control vulnerabilities — Sharkdropship for AliExpress Dropship and Affiliate 6.5 Medium 2024-12-09
CVE-2023-30873 WordPress WP Docs plugin <= 1.9.8 - Broken Access Control — WP Docs 5.4 Medium 2024-12-09
CVE-2023-31073 WordPress Shortcode to display post and user data plugin <= 1.2.0 - Broken Access Control vulnerability — Display custom fields in the frontend – Post and User Profile Fields 4.3 Medium 2024-12-09
CVE-2023-32094 WordPress Extended Post Status plugin <= 1.0.19 - Broken Access Control vulnerability — Extended Post Status 5.4 Medium 2024-12-09

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