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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8311 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-3216 WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels <= 4.4.2 - Missing Authorization to Unauthenticated Settings Reset — WebToffee WooCommerce PDF Invoices, Packing Slips, Delivery Notes & Shipping Labels 5.3 Medium 2024-04-06
CVE-2024-1994 Image Watermark <= 1.7.3 - Missing Authorization to Authenticated (Subscriber+) Watermark Modification — Image Watermark 4.3 Medium 2024-04-06
CVE-2024-27911 Lenovo Printer 安全漏洞 — Printers 7.5 High 2024-04-05
CVE-2024-27910 Lenovo Printer 安全漏洞 — Printers 5.3 Medium 2024-04-05
CVE-2024-0394 Rapid7 Minerva Armor Privilege Escalation — Minerva 7.8 High 2024-04-03
CVE-2024-1807 Product Sort and Display for WooCommerce <= 2.4.1 - Missing Authorization — Product Sort and Display for WooCommerce 6.5 Medium 2024-04-02
CVE-2024-1732 Sharkdropship for AliExpress Dropshipping and Affiliate <= 2.2.4 - Missing Authorization to Unauthenticated Arbitrary Post Deletion — Sharkdropship & affiliate for AliExpress 5.3 Medium 2024-04-02
CVE-2024-31099 WordPress Phlox Core Elements plugin <= 2.15.7 - Broken Access Control vulnerability — Shortcodes and extra features for Phlox theme 6.4 Medium 2024-04-01
CVE-2024-2086 Integrate Google Drive <= 1.3.8 - Missing Authorization to Unauthenticated Settings Modification and Export — File Manager for Google Drive – Integrate Google Drive 10.0 Critical 2024-03-30
CVE-2024-30463 WordPress BEAR plugin <= 1.1.4.3 - Broken Access Control vulnerability — BEAR 4.3 Medium 2024-03-29
CVE-2024-30477 WordPress Klarna Payments for WooCommerce plugin <= 3.2.4 - Broken Access Control vulnerability — Klarna Payments for WooCommerce 5.3 Medium 2024-03-29
CVE-2024-30508 WordPress WP Hotel Booking plugin <= 2.0.9.2 - Broken Access Control vulnerability — WP Hotel Booking 6.5 Medium 2024-03-29
CVE-2024-30505 WordPress Church Admin plugin <= 4.1.18 - Broken Access Control vulnerability — Church Admin 5.4 Medium 2024-03-29
CVE-2024-30487 WordPress MP3 Audio Player for Music, Radio & Podcast by Sonaar plugin <= 5.1 - Broken Access Control vulnerability — MP3 Audio Player for Music, Radio & Podcast by Sonaar 7.6 High 2024-03-29
CVE-2024-2848 Responsive <= 5.0.2 - Missing Authorization to HTML Injection — Responsive 7.5 High 2024-03-29
CVE-2024-2476 OceanWP <= 3.5.4 - Missing Authorization to Sensitive Information Exposure via Limited Local File Inclusion — OceanWP 4.3 Medium 2024-03-29
CVE-2024-2844 Easy Appointments <= 3.11.18 - Insufficient Authorization — Easy Appointments 4.3 Medium 2024-03-29
CVE-2024-29241 Synology Surveillance Station 安全漏洞 — Surveillance Station 9.9 Critical 2024-03-28
CVE-2024-29240 Synology Surveillance Station 安全漏洞 — Surveillance Station 4.3 Medium 2024-03-28
CVE-2024-29229 Synology Surveillance Station 安全漏洞 — Surveillance Station 7.7 High 2024-03-28
CVE-2024-29228 Synology Surveillance Station 安全漏洞 — Surveillance Station 7.7 High 2024-03-28
CVE-2024-28003 WordPress Max Mega Menu plugin <= 3.3 - Broken Access Control vulnerability — Max Mega Menu 5.4 Medium 2024-03-28
CVE-2024-28004 WordPress Colibri Page Builder plugin <= 1.0.248 - Broken Access Control vulnerability — Colibri Page Builder 5.4 Medium 2024-03-28
CVE-2024-2962 Networker - Tech News WordPress Theme with Dark Mode <= 1.1.9 - Missing Authorization — Networker - Tech News WordPress Theme with Dark Mode 5.3 Medium 2024-03-27
CVE-2023-52214 WordPress Void Contact Form 7 Widget For Elementor Page Builder plugin <= 2.3 - Broken Access Control vulnerability — Void Contact Form 7 Widget For Elementor Page Builder 4.3 Medium 2024-03-26
CVE-2024-22156 WordPress SalesKing plugin <= 1.6.15 - Unauthenticated Plugin Settings Change vulnerability — SalesKing 6.5 Medium 2024-03-26
CVE-2024-2906 WordPress Radio Player plugin <= 2.0.73 - Unauthenticated Broken Access Control vulnerability — Radio Player 6.5 Medium 2024-03-26
CVE-2024-30235 WordPress Multiple Page Generator Plugin – MPG plugin <= 3.4.0 - Broken Access Control vulnerability — Multiple Page Generator Plugin – MPG 4.3 Medium 2024-03-26
CVE-2024-30234 WordPress WholesaleX plugin <= 1.3.1 - Broken Access Control vulnerability — WholesaleX 6.5 Medium 2024-03-26
CVE-2024-23520 WordPress PopupAlly plugin <= 2.1.0 - Broken Access Control vulnerability — PopupAlly 4.3 Medium 2024-03-26

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