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-100417 RustDesk before 1.5.0 One-Way File Transfer Bypass — rustdesk 3.1 Low 2026-09-25
CVE-2026-100388 RustDesk before 1.5.0 Missing Authorization Check on Incoming File Clipboard Messages — rustdesk 5.4 Medium 2026-09-25
CVE-2026-100305 TDuck survey form through 6.0 Fill-In Restriction Bypass via Authenticated Submission Endpoint — tduck-survey-form 4.3 Medium 2026-09-25
CVE-2026-100303 TDuck survey form through 6.0 Missing Authorization in Form Theme Management Endpoints — tduck-survey-form 5.4 Medium 2026-09-25
CVE-2026-53625 GLPI: Privilege Escalation via authtype API manipulation — glpi 7.5 High 2026-09-25
CVE-2026-53627 GLPI: Unexpected access to update operations through the API — glpi 6.0 Medium 2026-09-25
CVE-2026-65828 Zammad: Pending upload deletion bypass via legacy attachment endpoint — zammad 2.3 Low 2026-09-25
CVE-2026-56730 Zammad: Missing authorization in GraphQL mutation for suggesting knowledge base answers — zammad 2.1 Low 2026-09-25
CVE-2026-56726 Zammad: Missing authorization check in GitHub + GitLab integration allows cross-ticket data leak — zammad 5.1 Medium 2026-09-25
CVE-2026-93365 Bludit CMS 3.22.0 Missing Authorization via content-get-list AJAX Endpoint — Bludit CMS 6.5 Medium 2026-09-25
CVE-2026-93363 Payload CMS storage-vercel-blob Adapter Improper Access Control on Upload Route — payload 4.3 Medium 2026-09-25
CVE-2026-67420 RabbitMQ OAuth credential refresh retains revoked runtime tags — rabbitmq-server 2.3 Low 2026-09-25
CVE-2026-67421 RabbitMQ: Stored HTML Injection in RabbitMQ Management OAuth Error Handling — rabbitmq-server 4.5 Medium 2026-09-25
CVE-2026-95835 Missing ownership check on the shared memory object named by the kitty askpass escape code — kitty 5.6 Medium 2026-09-25
CVE-2026-67407 RabbitMQ: Incomplete fix for CVE-2026-44838: `escape_regex_char/1` does not escape `-`, leaving room for an MQTT topic permission bypass — rabbitmq-server 5.1 Medium 2026-09-25
CVE-2026-80432 Missing authorization in the kitty drag and drop protocol allows a client to obtain dragged file contents without a drop — kitty 6.0 Medium 2026-09-25
CVE-2026-67412 RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message access — rabbitmq-server 6.0 Medium 2026-09-25
CVE-2026-67241 RabbitMQ: AMQP 1.0 management exchange.declare skips alternate-exchange permission check — rabbitmq-server 4.8 Medium 2026-09-25
CVE-2026-66078 RabbitMQ: protected tag bypass via bulk-delete — rabbitmq-server 2.1 Low 2026-09-25
CVE-2026-97898 Broken authorization in Akia keyless entry lets an authenticated guest unlock other rooms — akia 8.4 High 2026-09-25
CVE-2026-89406 Modula Image Gallery <= 3.0.1 - Missing Authorization to Unauthenticated Private Gallery Image Disclosure via 'modula_gallery_id' and 'modula_image_id' Parameters — Modula Image Gallery – Photo Grid & Video Gallery 7.5 High 2026-09-25
CVE-2026-92713 Modula Image Gallery <= 3.0.2 - Missing Authorization to Authenticated (Author+) Arbitrary File Deletion (Non-PHP) via 'file' Parameter — Modula Image Gallery – Photo Grid & Video Gallery 8.1 High 2026-09-25
CVE-2026-92829 Blog2Social: Social Media Auto Post & Scheduler <= 9.1.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Modification via Multiple AJAX Handlers — Blog2Social: Social Media Auto Post & Scheduler 4.3 Medium 2026-09-25
CVE-2026-19775 OpenStation <= 1.1.7 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via AI Copilot Search Endpoint — OpenStation: Desktop Windows, Dock & Virtual Desktops for WP Admin 4.3 Medium 2026-09-25
CVE-2026-89055 Customer Reviews for WooCommerce <= 5.120.0 - Missing Authorization to Unauthenticated Arbitrary Attachment Deletion via 'items[][media]' Parameter — Customer Reviews for WooCommerce 9.1 Critical 2026-09-25
CVE-2026-84302 Discourse: Non-participant moderators can read, edit, and delete PM content through Discourse AI reviewables — discourse 4.2 Medium 2026-09-24
CVE-2026-91160 OpenWA: A read-only API key can receive a session pairing QR over the WebSocket event stream — OpenWA 8.2 High 2026-09-24
CVE-2026-63203 Logto: Account API can disclose stored third-party provider tokens without the identities scope — logto 7.6 High 2026-09-24
CVE-2026-67233 RabbitMQ: Monitoring-tag user can DELETE shovels — rabbitmq-server 6.0 Medium 2026-09-24
CVE-2026-65422 Genetec Security Center 媒体网关 API 授权漏洞 — Genetec Security Center 6.5 Medium 2026-09-24

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