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-2024-54252 WordPress Pinpoint Booking System Plugin <= 2.9.9.5.7 - Broken Access Control vulnerability — Pinpoint Booking System 6.3 Medium 2024-12-13
CVE-2024-54242 WordPress Simple Notification plugin <= 1.3 - Broken Access Control vulnerability — Simple Notification 6.5 Medium 2024-12-13
CVE-2024-54241 WordPress Elite Notification plugin 1.5 - Cross Site Scripting (XSS) vulnerability — Elite Notification – Sales Popup, Social Proof, FOMO & WooCommerce Notification 6.5 Medium 2024-12-13
CVE-2024-54239 WordPress Eyewear prescription form plugin <= 4.0.18 - Arbitrary Option Update to Privilege Escalation vulnerability — Eyewear prescription form 9.8 Critical 2024-12-13
CVE-2023-44147 WordPress Comment Blacklist Updater plugin <= 1.1.0 - Broken Access Control vulnerability — Comment Blacklist Updater 5.3 Medium 2024-12-13
CVE-2023-44149 WordPress Brands for WooCommerce plugin <= 3.8.2.2 - Broken Access Control vulnerability — Brands for WooCommerce 5.3 Medium 2024-12-13
CVE-2023-44142 WordPress Inactive Logout plugin <= 3.2.2 - Broken Access Control vulnerability — Inactive Logout 5.4 Medium 2024-12-13
CVE-2023-41951 WordPress rtMedia for WordPress, BuddyPress and bbPress plugin <= 4.6.14 - Broken Access Control vulnerability — rtMedia for WordPress, BuddyPress and bbPress 4.3 Medium 2024-12-13
CVE-2023-41952 WordPress Fluent Forms plugin <= 5.0.8 - Broken Access Control vulnerability — FluentForm 5.3 Medium 2024-12-13
CVE-2023-41875 WordPress WP Directory Kit plugin <= 1.2.6 - Broken Access Control vulnerability — WP Directory Kit 5.3 Medium 2024-12-13
CVE-2023-41873 WordPress SAML Single Sign On – SSO Login plugin <= 5.0.4 - Broken Access Control vulnerability — SAML SP Single Sign On 4.3 Medium 2024-12-13
CVE-2023-41869 WordPress WP Accessibility Helper (WAH) plugin <= 0.6.2.4 - Broken Access Control vulnerability — WP Accessibility Helper (WAH) 4.3 Medium 2024-12-13
CVE-2023-41870 WordPress WP Crowdfunding plugin <= 2.1.5 - Broken Access Control vulnerability — WP Crowdfunding 4.3 Medium 2024-12-13
CVE-2023-41866 WordPress Automatic YouTube Gallery plugin <= 2.3.3 - Broken Access Control vulnerability — Automatic YouTube Gallery 4.3 Medium 2024-12-13
CVE-2023-41865 WordPress Slider Pro plugin <= 4.8.6 - Broken Access Control vulnerability — Slider Pro 4.3 Medium 2024-12-13
CVE-2023-41857 WordPress Click To Tweet plugin <= 2.0.14 - Broken Access Control vulnerability — Click To Tweet 5.4 Medium 2024-12-13
CVE-2023-41849 WordPress Posts Like Dislike plugin <= 1.1.0 - Broken Access Control vulnerability — Posts Like Dislike 5.3 Medium 2024-12-13
CVE-2023-41848 WordPress Carousel Slider plugin <= 2.2.2 - Broken Access Control vulnerability — Carousel Slider 5.3 Medium 2024-12-13
CVE-2023-41803 WordPress BitPay Checkout for WooCommerce plugin <= 4.1.0 - Broken Access Control vulnerability — BitPay Checkout for WooCommerce 5.3 Medium 2024-12-13
CVE-2023-41802 WordPress Super Socializer plugin <= 7.13.54 - Broken Access Control vulnerability — Super Socializer 4.3 Medium 2024-12-13
CVE-2023-41695 WordPress Analytify plugin <= 5.1.0 - Broken Access Control vulnerability — Analytify 3.5 Low 2024-12-13
CVE-2023-41690 WordPress WiserNotify Social Proof plugin <= 2.5 - Broken Access Control vulnerability — WiserNotify Social Proof 5.3 Medium 2024-12-13
CVE-2023-41688 WordPress Bulk NoIndex & NoFollow Toolkit plugin <= 1.5 - Broken Access Control vulnerability — Bulk NoIndex & NoFollow Toolkit 5.4 Medium 2024-12-13
CVE-2023-41689 WordPress Post to Google My Business (Google Business Profile) plugin <= 3.1.14 - Broken Access Control vulnerability — Post to Google My Business (Google Business Profile) 4.3 Medium 2024-12-13
CVE-2023-41683 WordPress TelSender plugin <= 1.14.11 - Broken Access Control + CSRF vulnerability — TelSender 5.4 Medium 2024-12-13
CVE-2023-41671 WordPress Abandoned Cart Lite for WooCommerce plugin <= 5.16.1 - Cross Site Request Forgery (CSRF) vulnerability — Abandoned Cart Lite for WooCommerce 5.4 Medium 2024-12-13
CVE-2023-41664 WordPress Easy Newsletter Signups plugin <= 1.0.4 - Broken Access Control vulnerability — Easy Newsletter Signups 6.5 Medium 2024-12-13
CVE-2023-41649 WordPress Ovic Product Bundle plugin <= 1.1.2 - Broken Access Control vulnerability — Ovic Product Bundle 6.5 Medium 2024-12-13
CVE-2023-41132 WordPress Category Slider for WooCommerce plugin <= 1.4.15 - Broken Access Control vulnerability — Category Slider for WooCommerce 4.3 Medium 2024-12-13
CVE-2023-41130 WordPress Premmerce User Roles plugin <= 1.0.12 - Broken Access Control vulnerability — Premmerce User Roles 8.1 High 2024-12-13

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