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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8304 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-80337 Unauthorized Cross-Chatbot Tool Invocation in HAVELSAN's Sef - AI Chatbot Platform — Sef - AI Chatbot Platform 5.3 Medium 2026-10-02
CVE-2026-104054 calcom cal.diy PBAC Permission BookingAccessService.ts doesUserIdHaveAccessToBooking authorization — cal.diy 6.3 Medium 2026-10-02
CVE-2026-93832 摩托罗拉系统应用权限导出漏洞 — Setup App 4.4 Medium 2026-10-01
CVE-2026-17053 SMBus callback-removal syscalls accept an unvalidated user pointer, letting user threads manipulate kernel callback state — zephyr 4.4 Medium 2026-10-01
CVE-2026-97280 WordPress Review Schema plugin 3.1.0 - Broken Access Control vulnerability — Review Schema 6.5 Medium 2026-10-01
CVE-2026-97297 WordPress Gratisfaction plugin <= 4.6.3 - Broken Access Control vulnerability — Gratisfaction 7.6 High 2026-10-01
CVE-2026-97281 WordPress WP Project Manager plugin <= 4.0.7 - Broken Access Control vulnerability — WP Project Manager 6.3 Medium 2026-10-01
CVE-2026-97277 WordPress Social Boost plugin <= 3.6.2 - Broken Access Control vulnerability — Social Boost 7.6 High 2026-10-01
CVE-2026-97258 WordPress Aruba Migration Tool plugin <= 1.0.4 - Broken Access Control vulnerability — Aruba Migration Tool 6.5 Medium 2026-10-01
CVE-2026-62073 WordPress WP Full Stripe Free plugin <= 8.5.6 - Broken Access Control vulnerability — WP Full Stripe Free 7.5 High 2026-10-01
CVE-2026-62063 WordPress WpTravelly plugin <= 2.3.1 - Broken Access Control vulnerability — WpTravelly 5.4 Medium 2026-10-01
CVE-2026-102390 WordPress AFFI – Affiliate Marketing for WooCommerce plugin <= 1.0.9 - Broken Access Control vulnerability — AFFI – Affiliate Marketing for WooCommerce 5.3 Medium 2026-10-01
CVE-2026-102381 WordPress Majestic Support plugin <= 1.2.0 - Broken Access Control vulnerability — Majestic Support 5.3 Medium 2026-10-01
CVE-2026-103341 WordPress Unlimited Elements For Elementor (Free Widgets, Addons, Templates) plugin <= 2.0.20 - Broken Access Control vulnerability — Unlimited Elements For Elementor (Free Widgets, Addons, Templates) 5.3 Medium 2026-10-01
CVE-2026-103340 WordPress Site Reviews plugin <= 8.3.2 - Broken Access Control vulnerability — Site Reviews 5.3 Medium 2026-10-01
CVE-2026-103274 Ghost 5.3.0 before 6.58.0 Unauthenticated Comment Read — Ghost 5.3 Medium 2026-10-01
CVE-2026-103269 Ghost 5.3.0 before 6.62.0 Missing Authorization via Post Excerpts — Ghost 5.3 Medium 2026-10-01
CVE-2026-103268 Ghost 1.0.0 before 6.62.0 Suspension Bypass via Password Reset — Ghost 8.8 High 2026-10-01
CVE-2026-103260 n8n before 2.39.6 and 2.40.x before 2.40.1 Approval Bypass via Send and Wait Node — n8n 4.0 Medium 2026-10-01
CVE-2026-103251 n8n before 1.123.80, 2.39.6, and 2.40.1 Package Install Validation Bypass via PubSub — n8n 7.1 High 2026-10-01
CVE-2026-103495 JetBrains YouTrack 2026.2前翻译重载越权漏洞 — YouTrack 4.3 Medium 2026-10-01
CVE-2026-103490 JetBrains YouTrack 2026.2.19422前权限提升漏洞 — YouTrack 7.2 High 2026-10-01
CVE-2026-103659 MISP: Object Distribution ACL Bypass via Event Flattening Exposes Organisation-Only Attributes — MISP 7.1 High 2026-10-01
CVE-2026-88999 Redux Framework <= 4.5.14 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Attachment Deletion via 'attachment_id' Parameter — Redux Framework 4.3 Medium 2026-10-01
CVE-2026-76147 Genians, Inc Genian NAC/ZTNA Remote Code Execution — Genian NAC 4.0.175 Release 5.9 Medium 2026-10-01
CVE-2026-76143 Genians, Inc Genian SSL PNS Multi Factor Authentication Bypass — Genian SSL PNS (frodo-core) 7.3 High 2026-10-01
CVE-2026-92245 Simply Schedule Appointments <= 1.6.12.32 - Missing Authorization to Unauthenticated Sensitive Information Exposure and Arbitrary Appointment Deletion via 'recursive' Parameter on the appointment_types REST Endpoint via Public Nonce — Simply Schedule Appointments 7.5 High 2026-10-01
CVE-2026-101879 OpenClaw Windows Node before 2026.7.1-3 Missing Authorization — OpenClaw Windows Node 6.5 Medium 2026-09-30
CVE-2026-102375 WordPress Optimole plugin <= 4.2.14 - Broken Access Control vulnerability — Optimole 6.5 Medium 2026-09-30
CVE-2026-102397 WordPress Ultimate Maps by Supsystic plugin <= 1.5.5 - Broken Access Control vulnerability — Ultimate Maps by Supsystic 6.5 Medium 2026-09-30

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