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-23725 WordPress Shortcodes by Angie Makes plugin <= 3.46 - Broken Access Control vulnerability — Shortcodes 4.3 Medium 2024-12-09
CVE-2023-23814 WordPress Calendar Event Multi View plugin <= 1.4.13 - Broken Access Control vulnerability — CP Multi View Event Calendar 3.8 Low 2024-12-09
CVE-2023-23823 WordPress Enhanced Text Widget plugin <= 1.5.8 - Broken Access Control vulnerability — Enhanced Text Widget 4.3 Medium 2024-12-09
CVE-2023-23825 WordPress Spectra – WordPress Gutenberg Blocks plugin <= 2.3.0 - Broken Access Control + CSRF on Import_WPforms vulnerability — Spectra 3.1 Low 2024-12-09
CVE-2023-23834 WordPress Spectra – WordPress Gutenberg Blocks plugin <= 2.3.0 - Broken Access Control + CSRF on Activate_Plugin vulnerability — Spectra 4.3 Medium 2024-12-09
CVE-2023-23868 WordPress Cost of Goods for WooCommerce plugin <= 2.8.6 - Broken Access Control vulnerability — Cost of Goods for WooCommerce 5.4 Medium 2024-12-09
CVE-2023-23886 WordPress WP-RecentComments plugin <= 2.2.7 - Broken Access Control vulnerability — WP-RecentComments 5.4 Medium 2024-12-09
CVE-2023-23887 WordPress Easy Google Analytics for WordPress plugin <= 1.6.0 - Broken Access Control vulnerability — Easy Google Analytics for WordPress 5.3 Medium 2024-12-09
CVE-2023-23893 WordPress Simple Giveaways plugin <= 2.48.0 - Broken Access Control vulnerability — Simple Giveaways 5.3 Medium 2024-12-09
CVE-2023-23895 WordPress WP Time Slots Booking Form plugin <= 1.1.82 - Broken Access Control vulnerability — WP Time Slots Booking Form 4.7 Medium 2024-12-09
CVE-2023-23975 WordPress Quick Event Manager plugin <= 9.7.4 - Broken Access Control vulnerability — Quick Event Manager 5.3 Medium 2024-12-09
CVE-2023-23986 WordPress Reviews and Rating – Google My Business plugin <= 4.14 - Broken Access Control vulnerability — Reviews and Rating – Google My Business 5.4 Medium 2024-12-09
CVE-2023-24375 WordPress WordPress Social Login and Register (Discord, Google, Twitter, LinkedIn) plugin <= 7.5.14 - Broken Access Control vulnerability — WordPress Social Login and Register (Discord, Google, Twitter, LinkedIn) 3.5 Low 2024-12-09
CVE-2023-24407 WordPress Booking calendar, Appointment Booking System plugin <= 3.2.3 - Broken Access Control vulnerability — Booking calendar, Appointment Booking System 5.0 Medium 2024-12-09
CVE-2023-25026 WordPress PayPal Brasil para WooCommerce plugin <= 1.4.2 - Broken Access Control vulnerability — PayPal Brasil para WooCommerce 4.3 Medium 2024-12-09
CVE-2023-25035 WordPress Quick Contact Form plugin <= 8.0.3.1 - Broken Access Control vulnerability — Quick Contact Form 6.5 Medium 2024-12-09
CVE-2023-25037 WordPress Booking Calendar Contact Form plugin <= 1.2.34 - Broken Access Control vulnerability — Booking Calendar Contact Form 4.3 Medium 2024-12-09
CVE-2023-25048 WordPress Fantastic Content Protector Free plugin <= 2.6 - Broken Access Control vulnerability — Fantastic Content Protector Free 5.3 Medium 2024-12-09
CVE-2023-25060 WordPress Album and Image Gallery plus Lightbox plugin <= 1.6.2 - Broken Access Control vulnerability — Album and Image Gallery plus Lightbox 5.3 Medium 2024-12-09
CVE-2023-25067 WordPress We’re Open! plugin <= 1.45 - Broken Access Control vulnerability — We’re Open! 4.3 Medium 2024-12-09
CVE-2023-25454 WordPress Protected Posts Logout Button plugin <= 1.4.5 - Broken Access Control vulnerability — Protected Posts Logout Button 6.5 Medium 2024-12-09
CVE-2023-25455 WordPress WordPress Social Login and Register (Discord, Google, Twitter, LinkedIn) plugin <= 7.6.0 - Arbitrary Content Deletion vulnerability — WordPress Social Login and Register (Discord, Google, Twitter, LinkedIn) 5.3 Medium 2024-12-09
CVE-2023-25469 WordPress Easy Table of Contents plugin <= 2.0.45.2 - Broken Access Control vulnerability — Easy Table of Contents 5.4 Medium 2024-12-09
CVE-2023-25486 WordPress Clone plugin <= 2.3.7 - Broken Access Control vulnerability — Clone 4.3 Medium 2024-12-09
CVE-2023-25703 WordPress Meta slider and carousel with lightbox plugin <= 1.6.2 - Broken Access Control vulnerability — Meta slider and carousel with lightbox 5.3 Medium 2024-12-09
CVE-2023-25714 WordPress Quick Paypal Payments plugin <= 5.7.25 - Broken Access Control vulnerability — Quick Paypal Payments 7.5 High 2024-12-09
CVE-2023-25959 WordPress Apollo13 Framework Extensions plugin <= 1.8.10 - Broken Access Control — Apollo13 Framework Extensions 5.4 Medium 2024-12-09
CVE-2023-25791 WordPress Fontiran plugin <= 2.1 - Broken Access Control vulnerability — Fontiran 5.4 Medium 2024-12-09
CVE-2023-25966 WordPress FileBird plugin <= 5.1.4 - Broken Access Control vulnerability — Filebird 5.5 Medium 2024-12-09
CVE-2023-25993 WordPress Top 10 – Popular posts plugin for WordPress plugin <= 3.2.3 - Broken Access Control vulnerability — Top 10 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.