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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

5582 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)
ConfidentialityRead 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.
IntegrityModify 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 ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
AvailabilityDoS: 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 DesignDivide 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 DesignEnsure 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 DesignUse 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 DesignFor 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, InstallationUse 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 IDTitleCVSSSeverityPublished
CVE-2023-4700 Missing Authorization in GitLab — GitLab 3.5 Low2023-11-06
CVE-2023-4198 Dolibarr ERP CRM (<= 17.0.3) Improper Access Control — Dolibarr ERP CRM 6.5 Medium2023-11-01
CVE-2022-3007 Unauthorized Access Vulnerability in Syska SW100 Smartwatch — Syska SW100 Smartwatch 8.1 High2023-10-31
CVE-2023-5862 Missing Authorization in hamza417/inure — hamza417/inure 8.8 -2023-10-31
CVE-2023-5251 Grid Plus <= 1.3.2 - Missing Authorization to Authenticated (Subscriber+) Grid Layout Add/Update/Delete — Grid Plus – Unlimited grid layout 5.4 Medium2023-10-30
CVE-2023-5425 Post Meta Data Manager <=1.2.0 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation — Post Meta Data Manager 8.8 High2023-10-28
CVE-2023-5426 Post Meta Data Manager <=1.2.0 - Missing Authorization to User, Term, and Post Meta Deletion — Post Meta Data Manager 7.5 High2023-10-28
CVE-2023-37910 org.xwiki.platform:xwiki-platform-attachment-api vulnerable to Missing Authorization on Attachment Move — xwiki-platform 8.1 High2023-10-25
CVE-2023-43488 Bosch ctrlX HMI Web Panel WR21 安全漏洞 — ctrlX HMI Web Panel - WR21 (WR2107) 7.9 High2023-10-25
CVE-2023-5311 WP EXtra <= 6.2 - Missing Authorization to .htaccess File Modification — WP EXtra – One Click Optimize 8.8 High2023-10-25
CVE-2023-4606 Lenovo XClarity Controller 安全漏洞 — Lenovo XClarity Controller (XCC) 8.1 High2023-10-24
CVE-2023-5132 Soisy Pagamento Rateale <= 6.0.1 - Missing Authorization to Sensitive Information Exposure — Soisy Pagamento Rateale 7.5 High2023-10-21
CVE-2022-3622 Blog2Social <= 6.9.11 - Missing Authorization to Authenticated (Subscriber+) Settings Update — Blog2Social: Social Media Auto Post & Scheduler 4.1 Medium2023-10-20
CVE-2023-4668 Ad Inserter <= 2.7.30 - Unauthenticated Sensitive Information Exposure via ai-debug-processing-fe — Ad Inserter – Ad Manager & AdSense Ads 5.3 Medium2023-10-20
CVE-2023-4941 BEAR <= 1.1.3.3 - Missing Authorization to Product Manipulation — BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net 4.3 Medium2023-10-20
CVE-2023-5533 AI ChatBot <= 4.8.9 and 4.9.2 - Missing Authorization on AJAX actions — WPBot – AI ChatBot for Live Support, Lead Generation, AI Services 5.3 Medium2023-10-20
CVE-2022-4943 miniOrange's Google Authenticator <= 5.6.5 - Missing Authorization to Plugin Settings Change — miniOrange 2FA – Two-Factor Authentication for WordPress (SMS, Email & Google Authenticator) 7.5 High2023-10-20
CVE-2023-4943 BEAR <= 1.1.3.3 - Missing Authorization to Product Manipulation — BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net 4.3 Medium2023-10-20
CVE-2023-4947 WooCommerce EAN Payment Gateway < 6.1.0 - Missing Authorization to Authenticated (Contributor+) EAN Update — WooCommerce EAN Payment Gateway 4.3 Medium2023-10-20
CVE-2020-36698 Security & Malware scan by CleanTalk <= 2.50 - Missing Authorization — Login Security, FireWall, Malware removal by CleanTalk 8.8 High2023-10-20
CVE-2023-4645 Ad Inserter <= 2.7.30 - Unauthenticated Sensitive Information Exposure via ai_ajax — Ad Inserter – Ad Manager & AdSense Ads 5.3 Medium2023-10-19
CVE-2023-4938 BEAR <= 1.1.3.3 - Missing Authorization to Product Manipulation — BEAR – Bulk Editor and Products Manager Professional for WooCommerce by Pluginus.Net 4.3 Medium2023-10-18
CVE-2023-42473 Missing Authorization Check In S/4HANA (Manage Withholding Tax Items) — S/4HANA (Manage Withholding Tax Items) 5.4 Medium2023-10-10
CVE-2023-43700 SICK APU 安全漏洞 — APU0200 7.7 High2023-10-09
CVE-2023-45247 Acronis Agent 安全漏洞 — Acronis Cyber Protect Cloud Agent 8.1 -2023-10-09
CVE-2023-5331 File Information Leak via IDOR in file_id in Draft Posts — Mattermost 4.3 Medium2023-10-09
CVE-2023-45246 Acronis Agent 授权问题漏洞 — Acronis Cyber Protect Cloud Agent 9.1 -2023-10-06
CVE-2023-45245 Acronis Agent 安全漏洞 — Acronis Agent 6.5 -2023-10-06
CVE-2023-45244 Acronis Agent 安全漏洞 — Acronis Cyber Protect Cloud Agent 9.1 -2023-10-06
CVE-2023-4469 Profile Extra Fields by BestWebSoft <= 1.2.7 - Missing Authorization to Sensitive Information Exposure — Profile Extra Fields by BestWebSoft 5.3 Medium2023-10-06

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