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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8307 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-79286 Google Chrome 授权问题漏洞 — Chrome - - 2026-08-25
CVE-2026-79104 Google Chrome 授权问题漏洞 — Chrome - - 2026-08-25
CVE-2026-79044 Google Chrome 授权问题漏洞 — Chrome - - 2026-08-25
CVE-2026-79212 Google Chrome 授权问题漏洞 — Chrome - - 2026-08-25
CVE-2026-70550 Potential unauthorized access to private Composer repository metadata in JFrog Artifactory — artifactory 6.5 Medium 2026-08-25
CVE-2026-69104 Potential unauthorized repository migration in JFrog Artifactory — artifactory 7.6 High 2026-08-25
CVE-2026-55541 PraisonAI: `--api-key` flag on `praisonai serve` is not properly enforced — PraisonAI 8.8 High 2026-08-25
CVE-2026-55530 PraisonAI: ast_grep_rewrite rewrites arbitrary files without the @require_approval gate enforced on every sibling mutation tool — PraisonAI 6.1 Medium 2026-08-25
CVE-2026-79672 Ech0 before 4.4.3 Authentication Bypass via Comment Panel — Ech0 5.5 Medium 2026-08-25
CVE-2026-79669 Ech0 before 4.4.3 Missing Authorization on System Logs — Ech0 4.3 Medium 2026-08-25
CVE-2026-79666 Ech0 before 4.4.3 Missing Authorization via dashboard log endpoints — Ech0 6.5 Medium 2026-08-25
CVE-2026-79665 Ech0 before 4.5.1 Authorization Bypass via Session Tokens — Ech0 8.8 High 2026-08-25
CVE-2026-17587 My Agile Privacy® <= 3.3.6 - Missing Authorization to Unauthenticated Plugin Settings Modification via map_missing_cookie_shield / map_check_consent_mode_status AJAX Actions — My Agile Privacy® – CMP, Cookie Consent & Privacy Tools 5.3 Medium 2026-08-25
CVE-2026-75908 Newsletters <= 4.17 - Missing Authorization to Authenticated (Author+) Arbitrary Modification via 'newsletters_mailinglistsroles' POST Parameter — Newsletters 4.3 Medium 2026-08-25
CVE-2026-79652 Keycloak-services: keycloak-services: jwt bearer authorization grant does not enforce consentrequired — Red Hat build of Keycloak 26.6 5.9 Medium 2026-08-25
CVE-2026-56092 Broken Access Control in extension "Apache Solr for TYPO3 - Enterprise Search" (solr) — Extension "Apache Solr for TYPO3 - Enterprise Search" 7.6 High 2026-08-25
CVE-2026-77128 Broken Access Control in extension "Event management and registration" (sf_event_mgt) — Extension "Event management and registration" 6.3 Medium 2026-08-25
CVE-2026-77133 Broken Access Control in extension "femanager" (femanager) — Extension "femanager" 6.0 Medium 2026-08-25
CVE-2026-77140 Broken Access Control in extension "Telephone Directory" (telephonedirectory) — Extension "Telephone Directory" 8.7 High 2026-08-25
CVE-2026-77141 Broken Access Control in extension "Club Directory" (clubdirectory) — Extension "Club Directory" 8.8 High 2026-08-25
CVE-2026-77142 Broken Access Control in extension "Industry Directory" (yellowpages2) — Extension "Industry Directory" 8.8 High 2026-08-25
CVE-2026-77143 Broken Access Control in extension "Forum" (pforum) — Extension "Forum" 8.8 High 2026-08-25
CVE-2026-77146 Broken Access Control in extension "femanager" (femanager) — Extension "femanager" 8.3 High 2026-08-25
CVE-2026-17548 Missing authorization for viewing background jobs — Checkmk 5.3 Medium 2026-08-25
CVE-2026-66109 Sky Co SKYSEA Client View 授权问题漏洞 — SKYSEA Client View 8.5 High 2026-08-25
CVE-2026-19892 InfusedWoo Pro <= 5.1.18 - Authenticated (Subscriber+) Privilege Escalation via Password Reset Link Disclosure — InfusedWoo Pro 8.8 High 2026-08-25
CVE-2026-75930 FundEngine <= 1.8.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Modification via 'campaign_post' Parameter — FundEngine – Donation and Crowdfunding Platform 4.3 Medium 2026-08-25
CVE-2026-75982 LearnPress <= 4.4.4 - Missing Authorization to Authenticated (Editor+) Limited Option Update via 'field_name' Parameter — LearnPress – WordPress LMS Plugin for Create and Sell Online Courses 4.4 Medium 2026-08-25
CVE-2026-10627 Events Manager <= 7.4.0 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'status', 'private', and 'private_only' Parameters — Events Manager – Calendar, Bookings, Tickets, and more! 5.3 Medium 2026-08-25
CVE-2026-56707 Grav Flex Objects 1.4.0 through 1.4.7 Authorization Bypass via Shortcode — grav 7.7 High 2026-08-25

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