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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6813 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-2026-75027 Themify Builder <= 7.8.0 - Missing Authorization to Unauthenticated Arbitrary Builder Data Modification via 'tb_update_old_data' AJAX Action — Themify Builder 5.3 Medium2026-08-22
CVE-2026-76074 AutomatorWP <= 5.8.4 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via automatorwp_campaign_monitor_get_lists AJAX Action — AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress 4.3 Medium2026-08-22
CVE-2026-76057 AutomatorWP <= 5.8.4 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via automatorwp_convertkit_get_forms AJAX Action — AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress 4.3 Medium2026-08-22
CVE-2026-34836 Combodo iTop: Improper access control in ajax.render.php and ajax.document.php — iTop 6.5 Medium2026-08-21
CVE-2026-53487 Kite has an authenticated cluster RBAC bypass in /api/v1/overview — kite 4.3 Medium2026-08-21
CVE-2026-33047 Combodo iTop: Object can be locked by a user without write permissions — iTop 4.3 Medium2026-08-21
CVE-2026-31936 Combodo iTop: Unauthorized access to object information via search operation — iTop 8.8 High2026-08-21
CVE-2026-76876 Craftplan < 0.5.1 Broken Access Control Information Disclosure via Settings API — craftplan 5.9 Medium2026-08-21
CVE-2026-75932 Jet Admin tenant isolation failure — Jet Admin 8.6 High2026-08-21
CVE-2026-77087 Paperclip before 0.3.1 Remote Code Execution via DNS Rebinding — paperclip 9.6 Critical2026-08-21
CVE-2026-62940 Incus has a project restriction bypass via instance migration config override — incus 9.9 Critical2026-08-21
CVE-2026-48751 Incus has a restricted project bypass leading to arbitrary command execution — incus 9.9 Critical2026-08-21
CVE-2026-77767 Reconmap Report Preview Endpoint Is Marked AllowAnonymous, Exposing Every Project and Client Organisation Without Authentication — reconmap 7.5 High2026-08-21
CVE-2026-50222 Apache CloudStack: Improper access control in Userdata reference APIs — Apache CloudStack--2026-08-21
CVE-2026-66721 Apache CloudStack: Authorization issue with listHostTags for domain admins — Apache CloudStack--2026-08-21
CVE-2026-72843 EverShop Missing Authorization on PATCH /api/customers/:id Allows Unauthenticated Account Takeover — evershop 9.8 Critical2026-08-20
CVE-2026-54509 TREK IDOR: any authenticated user can read another user's journey share token (full journey leak) — TREK 6.5 Medium2026-08-20
CVE-2026-19755 NoSleep 1.5.1 - Unauthorized disclosure of root-owned files through privileged XPC helper — NoSleep 6.9 Medium2026-08-20
CVE-2026-53569 Frappe: Missing authorization in toggle_like and mark_as_seen — frappe 5.3 Medium2026-08-20
CVE-2026-55095 OpenProject: Inplace-edit dialog exposes comments from hidden admin-only project custom fields — openproject 5.3 Medium2026-08-20
CVE-2026-64965 Missing Authorization Check in ATutor — ATutor 5.3 Medium2026-08-20
CVE-2026-76633 WeGIA < 3.9.2 Authorization Bypass Password Change via alterarSenha — WeGIA 8.1 High2026-08-20
CVE-2026-28163 WordPress New User Approve plugin <= 3.2.8 - Broken Access Control vulnerability — New User Approve 5.3 Medium2026-08-20
CVE-2026-74020 WordPress Koji theme <= 2.2.1 - Broken Access Control vulnerability — Koji 7.5 High2026-08-20
CVE-2026-74019 WordPress EPROLO Dropshipping plugin <= 2.4.2 - Broken Access Control vulnerability — EPROLO Dropshipping 7.1 High2026-08-20
CVE-2026-66647 WordPress Homlisti theme <= 3.1.2 - Broken Access Control vulnerability — Homlisti 6.5 Medium2026-08-20
CVE-2026-66595 WordPress WP Data Access plugin <= 5.5.80 - Broken Access Control vulnerability — WP Data Access 5.9 Medium2026-08-20
CVE-2025-53999 WordPress Altair theme <= 5.2.2 - Broken Access Control vulnerability — Altair 6.5 Medium2026-08-20
CVE-2026-74021 WordPress Chaplin theme <= 2.6.8 - Broken Access Control vulnerability — Chaplin 7.5 High2026-08-20
CVE-2026-17153 AI Agent by SiteGround <= 1.2.7 - Missing Authorization to Authenticated (Contributor+) Arbitrary Media Upload via /generate-content REST Endpoint — AI Agent by SiteGround 5.3 Medium2026-08-20

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