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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6842 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-2026-72799 SiYuan before v3.7.4 Information Disclosure via Path Resolution — siyuan 5.8 Medium 2026-08-12
CVE-2026-72800 SiYuan before v3.7.4 Information Disclosure via Unfiltered API — siyuan 5.8 Medium 2026-08-12
CVE-2026-72798 SiYuan before v3.7.4 Information Disclosure via renderAttributeView — siyuan 8.6 High 2026-08-12
CVE-2026-72797 SiYuan before v3.7.4 Information Disclosure via getEncryptedNotebookStatus — siyuan 5.8 Medium 2026-08-12
CVE-2026-72796 SiYuan before v3.7.4 Access Control Bypass via Static Routes — siyuan 5.8 Medium 2026-08-12
CVE-2026-72795 SiYuan before v3.7.4 Information Disclosure via Embed Block — siyuan 8.6 High 2026-08-12
CVE-2026-72791 SiYuan before v3.7.4 Information Disclosure via getAttributeViewFieldViews — siyuan 5.8 Medium 2026-08-12
CVE-2026-72790 SiYuan before v3.7.4 Information Disclosure via getNotebookInfo — siyuan 5.8 Medium 2026-08-12
CVE-2026-72789 SiYuan before v3.7.4 Authentication Bypass via Encrypted Notebooks — siyuan 8.6 High 2026-08-12
CVE-2026-4879 Missing Authorization in GitLab — GitLab 4.3 Medium 2026-08-12
CVE-2026-6821 Missing Authorization in GitLab — GitLab 4.3 Medium 2026-08-12
CVE-2026-16494 Missing Authorization in GitLab — GitLab 7.1 High 2026-08-12
CVE-2026-73301 Budibase: Missing RBAC on GET /api/global/groups allows BASIC users to enumerate all tenant groups and role mappings — budibase 4.3 Medium 2026-08-12
CVE-2026-18244 Missing Authorization in GitLab — GitLab 4.3 Medium 2026-08-12
CVE-2026-69107 Potential unauthorized artifact access in JFrog Artifactory — artifactory 5.9 Medium 2026-08-12
CVE-2026-68971 Apache Airflow: Cross-team authorization bypass in the asset materialization and dag-run result endpoints — Apache Airflow - - 2026-08-12
CVE-2026-65938 WhatsUp Gold versions prior to 26.0.2 contain an improper authorization vulnerability in the Scheduled Reports API. — WhatsUp Gold 4.3 Medium 2026-08-12
CVE-2026-70547 Potential unauthorized metadata exposure in JFrog Artifactory — artifactory 4.3 Medium 2026-08-12
CVE-2026-65926 Private Release Bundle versions may be disclosed under specific configurations — artifactory 3.1 Low 2026-08-12
CVE-2026-68758 Authenticated users may access restricted Artifactory support information — artifactory 6.5 Medium 2026-08-12
CVE-2026-66375 Low-privilege users may remove protected Artifactory metadata — artifactory 8.1 High 2026-08-12
CVE-2026-66379 Authenticated users may view private Puppet module metadata — artifactory 4.3 Medium 2026-08-12
CVE-2026-66378 Authenticated users may access private NuGet metadata — artifactory 4.3 Medium 2026-08-12
CVE-2026-66377 Anonymous users may access restricted Artifactory repository information — artifactory 5.3 Medium 2026-08-12
CVE-2026-66380 Authenticated users may access private OCI referrer metadata — artifactory 4.3 Medium 2026-08-12
CVE-2026-68754 Publishers without delete permission can overwrite docker layer information — artifactory 6.5 Medium 2026-08-12
CVE-2026-68753 Anonymous users may access restricted Artifactory content under specific configurations — artifactory 5.3 Medium 2026-08-12
CVE-2026-73287 RustFS: FTPS MKD bypasses IAM CreateBucket authorization — rustfs 5.4 Medium 2026-08-12
CVE-2026-73265 RustFS: Version-specific object reads authorize the non-version action — rustfs 6.5 Medium 2026-08-12
CVE-2026-73405 Authorization Bypass in SSE Pub/Sub Allows Unconfirmed Accounts to Access Stream Events in vulnerability-lookup — vulnerability-lookup 5.3 Medium 2026-08-12

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