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-48286 WordPress Accept Stripe Payments plugin <= 2.0.79 - Broken Access Control vulnerability — Stripe Payments 8.2 High 2024-12-09
CVE-2023-48287 WordPress TextMe SMS plugin <= 1.9.0 - Broken Access Control vulnerability — TextMe SMS 5.4 Medium 2024-12-09
CVE-2023-48324 WordPress Awesome Support HelpDesk plugin <= 6.1.4 - Broken Access control vulnerability — Awesome Support 5.4 Medium 2024-12-09
CVE-2023-48332 WordPress Mail Bank – #1 Mail SMTP Plugin for WordPress plugin <= 4.0.14 - Broken Access Control vulnerability — Mail Bank - #1 Mail SMTP Plugin for WordPress 4.3 Medium 2024-12-09
CVE-2023-48740 WordPress Easy Social Feed plugin <= 6.5.1 - Broken Access Control vulnerability — Easy Social Feed 4.3 Medium 2024-12-09
CVE-2023-48750 WordPress Void Elementor Post Grid Addon for Elementor Page builder plugin <= 2.1.10 - Broken Access Control vulnerability — Void Elementor Post Grid Addon for Elementor Page builder 5.3 Medium 2024-12-09
CVE-2023-48774 WordPress IdeaPush plugin < 8.58 - Broken Access Control vulnerability — IdeaPush 5.4 Medium 2024-12-09
CVE-2023-48776 WordPress canvasio3D Light plugin <= 2.5.0 - Broken Access Control vulnerability — canvasio3D Light 5.4 Medium 2024-12-09
CVE-2023-48779 WordPress 360 Javascript Viewer plugin <= 1.7.11 - Broken Access Control vulnerability — 360 Javascript Viewer 6.5 Medium 2024-12-09
CVE-2023-49154 WordPress Button Generator – easily Button Builder plugin <= 2.3.8 - Broken Access Control vulnerability — Button Generator – easily Button Builder 5.3 Medium 2024-12-09
CVE-2023-49156 WordPress GoDaddy Email Marketing plugin <= 1.4.3 - Broken Access Control vulnerability — GoDaddy Email Marketing 4.3 Medium 2024-12-09
CVE-2023-49167 WordPress Database for CF7 plugin <= 1.2.4 - Broken Access Control vulnerability — Database for CF7 6.5 Medium 2024-12-09
CVE-2023-49192 WordPress Enhanced Text Widget plugin <= 1.6.3 - Broken Access Control vulnerability — Enhanced Text Widget 5.3 Medium 2024-12-09
CVE-2023-49193 WordPress Grow Social plugin <= 1.30.0 - Broken Access Control vulnerability — Hubbub Lite 5.3 Medium 2024-12-09
CVE-2023-49196 WordPress Pagelayer plugin <= 1.7.7 - Broken Access Control vulnerability — PageLayer 4.3 Medium 2024-12-09
CVE-2023-49754 WordPress Bulk Edit Post Titles plugin <= 5.0.0 - Broken Access Control vulnerability — Bulk Edit Post Titles 4.3 Medium 2024-12-09
CVE-2023-49756 WordPress Eventin plugin <= 3.3.52 - Authenticated Notice Dismissal Vulnerability — Eventin 5.4 Medium 2024-12-09
CVE-2023-49755 WordPress Elementor Timeline Widget plugin <= 2.2 - Notice Dismissal Vulnerability — Elementor Timeline Widget 5.4 Medium 2024-12-09
CVE-2023-49757 WordPress Awesome Support plugin <= 6.1.10 - Broken Access Control + CSRF vulnerability — Awesome Support 5.4 Medium 2024-12-09
CVE-2023-49758 WordPress WP Booking System plugin <= 2.0.19.2 - Broken Access Control vulnerability — WP Booking System 4.3 Medium 2024-12-09
CVE-2023-49817 WordPress Flexible Woocommerce Checkout Field Editor plugin <= 2.0.1 - Broken Access Control vulnerability — Flexible Woocommerce Checkout Field Editor 8.2 High 2024-12-09
CVE-2023-49818 WordPress Webflow Pages plugin <= 1.0.8 - Broken Access Control vulnerability — Webflow Pages 5.3 Medium 2024-12-09
CVE-2023-49861 WordPress Social Media Feather plugin <= 2.1.3 - Broken Access Control vulnerability — Social Media Feather 4.3 Medium 2024-12-09
CVE-2023-49831 WordPress RegistrationMagic plugin <= 5.2.3.0 - Broken Access Control vulnerability — RegistrationMagic 7.5 High 2024-12-09
CVE-2023-49859 WordPress Login With Ajax plugin <= 4.1 - Broken Access Control vulnerability — Login With Ajax 4.3 Medium 2024-12-09
CVE-2023-49832 WordPress Site Reviews plugin <= 6.10.2 - Broken Access Control vulnerability — Site Reviews 5.3 Medium 2024-12-09
CVE-2023-49835 WordPress Post Duplicator plugin <= 2.31 - Broken Access Control vulnerability — Post Duplicator 4.3 Medium 2024-12-09
CVE-2023-49858 WordPress Custom Login plugin <= 4.1.0 - Broken Access Control vulnerability — Custom Login 4.3 Medium 2024-12-09
CVE-2023-49848 WordPress Sharkdropship dropshipping for Aliexpress, eBay, Amazon, etsy plugin <= 2.1.1 - Broken Access Control vulnerability — Sharkdropship dropshipping for Aliexpress, eBay, Amazon, etsy 6.5 Medium 2024-12-09
CVE-2023-49849 WordPress Shortcoder plugin <= 6.3 - Broken Access Control vulnerability — Shortcoder 4.3 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.