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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6817 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-2353 CHP Ads Block Detector <= 3.9.4 - Missing Authorization to Plugin Settings Update — CHP Ads Block Detector 4.3 Medium 2023-08-31
CVE-2023-3999 Waiting: One-click countdowns <= 0.6.2 - Missing Authorization — Waiting: One-click countdowns 6.3 Medium 2023-08-31
CVE-2023-4245 WooCommerce PDF Invoice Builder <= 1.2.89 - Missing Authorization to Sensitive Information Exposure — PDF Builder for WooCommerce. Create invoices,packing slips and more 4.3 Medium 2023-08-31
CVE-2023-4302 Missing permission checks in Fortify Plugin allow capturing credentials — Jenkins Fortify Plugin 4.2 Medium 2023-08-21
CVE-2023-4434 Missing Authorization in hamza417/inure — hamza417/inure 8.8 - 2023-08-20
CVE-2023-3244 Comments Like Dislike <= 1.2.0 - Missing Authorization to Authenticated (Subscriber+) Plugin Setting Reset — Comments Like Dislike 4.3 Medium 2023-08-17
CVE-2023-4374 WP Remote Users Sync <= 1.2.11 - Missing Authorization to Authenticated (Subscriber+) Log View — WP Remote Users Sync 4.3 Medium 2023-08-16
CVE-2023-40027 Conditionally missing authorization in @keystone-6/core — keystone 3.7 Low 2023-08-15
CVE-2023-39438 Missing Authorization check allows certain operations on CLA Assistant data — CLA Assistant 8.1 High 2023-08-15
CVE-2023-4106 A guest user can perform various actions on public playbooks — Mattermost 6.3 Medium 2023-08-11
CVE-2023-4105 Attachment of deleted message in a thread remains accessible and downloadable — Mattermost 3.1 Low 2023-08-11
CVE-2023-39966 1Panel arbitrary file write vulnerability exists in the background — 1Panel 7.5 High 2023-08-10
CVE-2023-4282 EmbedPress <= 3.8.2 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Delete via admin_post_remove and remove_private_data — EmbedPress – PDF Embedder, Embed YouTube Videos, 3D FlipBook, Social feeds, Docs & more 5.4 Medium 2023-08-10
CVE-2023-37862 PHOENIX CONTACT: Missing Authorization in WP 6xxx Web panels — WP 6070-WVPS 8.2 High 2023-08-09
CVE-2023-37860 PHOENIX CONTACT: Missing Authorization in WP 6xxx Web panels — WP 6070-WVPS 7.5 High 2023-08-09
CVE-2023-4124 Missing Authorization in answerdev/answer — answerdev/answer - - 2023-08-03
CVE-2023-0958 Inisev Plugins (Various Versions) - Missing Authorization on handle_installation function — Redirection 4.3 Medium 2023-07-28
CVE-2023-38510 Tolgee Lacks Permission Check for API Key for some endpoints — tolgee-platform 8.1 High 2023-07-27
CVE-2023-3956 InstaWP Connect <= 0.0.9.18 - Missing Authorization to Unauthenticated Post/Taxonomy/User Add/Change/Delete, Customizer Setting Change, Plugin Installation/Activation/Deactication via events_receiver — InstaWP Connect – 1-click WP Staging & Migration 9.8 Critical 2023-07-27
CVE-2023-3442 Missing Authorization in Jenkins plug-in for ServiceNow DevOps — Jenkins plug-in for ServiceNow DevOps 7.7 High 2023-07-26
CVE-2023-3714 ProfileGrid <= 5.5.2 - Missing Authorization to Arbitrary Group Option Modification and Privilege Escalation — ProfileGrid – User Profiles, Groups and Communities 7.5 High 2023-07-18
CVE-2023-3403 ProfileGrid <= 5.5.1 - Missing Authorization to User Import — ProfileGrid – User Profiles, Groups and Communities 5.4 Medium 2023-07-18
CVE-2023-3713 ProfileGrid <= 5.5.1 - Authenticated (Subscriber+) Arbitrary Option Update — ProfileGrid – User Profiles, Groups and Communities 8.8 High 2023-07-18
CVE-2023-3587 Inconsistent state in UI after boards permission change by system admin — Mattermost 2.7 Low 2023-07-17
CVE-2023-2268 Plane v0.7.1 - Unauthorized access to files — Plane 7.1 High 2023-07-15
CVE-2023-2561 Gallery Metabox <= 1.5 - Missing Authorization via gallery_remove — Gallery Metabox 4.3 Medium 2023-07-12
CVE-2023-2869 WP-Members Membership <= 3.4.7.3 - Missing Authorization to Settings Update — WP-Members Membership Plugin 4.3 Medium 2023-07-12
CVE-2023-2562 Gallery Metabox <= 1.5 - Missing Authorization via refresh_metabox — Gallery Metabox 4.3 Medium 2023-07-12
CVE-2023-33992 Missing Authorization Check in SAP Business Warehouse and SAP BW/4HANA — SAP Business Warehouse and SAP BW/4HANA 4.5 Medium 2023-07-11
CVE-2023-2078 Buy Me a Coffee – Button and Widget Plugin <= 3.7 - Missing Authorization — Buy Me a Coffee – Button and Widget Plugin 7.3 High 2023-07-11

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