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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6896 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-28554 wpForo Forum 2.4.14 Missing Authorization via Post Approval AJAX Handler — wpForo Forum 4.3 Medium 2026-02-28
CVE-2026-28424 Statamic's missing authorization allows access to email addresses — cms 6.5 Medium 2026-02-27
CVE-2026-28515 openDCIM <= 23.04 Missing Authorization in install.php — openDCIM 8.8 - 2026-02-27
CVE-2026-28408 WeGIA lacks authentication verification in adicionar_tipo_docs_atendido.php — WeGIA 9.8 Critical 2026-02-27
CVE-2026-27836 phpMyFAQ Allows Unauthenticated Account Creation via WebAuthn Prepare Endpoint — phpMyFAQ 7.5 High 2026-02-27
CVE-2026-27792 Seerr missing authentication on pushSubscription endpoints — seerr 5.4 Medium 2026-02-27
CVE-2026-28217 IDOR in GraphQL userCollection Query Exposes Other Users' Private Collections — hoppscotch 6.5 Medium 2026-02-26
CVE-2026-27638 ActualBudget missing authorization in sync endpoints allows cross-user budget file access in multi-user mode — actual 8.1AI High AI 2026-02-26
CVE-2026-27457 Weblate: Missing access control for the AddonViewSet API exposes all addon configurations — weblate 4.3 Medium 2026-02-26
CVE-2026-27151 Discourse doesn't validate destination topic when moving posts — discourse 4.3AI Medium AI 2026-02-26
CVE-2026-27150 Discourse doesn't ensure guardian check when creating QueryGroupBookmark — discourse 4.3AI Medium AI 2026-02-26
CVE-2026-27021 Discourse: Poll voters endpoint lacked post visibility checks — discourse 5.3AI Medium AI 2026-02-26
CVE-2026-26979 Discourse: TL4 users are able to change status of restricted topics — discourse 5.4AI Medium AI 2026-02-26
CVE-2026-26207 DIscourse's discourse-policy plugin lacks post access check — discourse 5.4 Medium 2026-02-26
CVE-2026-24004 Fleet: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint — fleet 8.2AI High AI 2026-02-26
CVE-2026-27954 LiveHelperChat has department-level authorization bypass in holdaction, blockuser, and transferchat endpoints — livehelperchat 8.8AI High AI 2026-02-26
CVE-2026-27946 ZITADEL Users Can Self-Verify Email/Phone via UpdateHumanUser API — zitadel 4.3AI Medium AI 2026-02-26
CVE-2025-14103 Missing Authorization in GitLab — GitLab 4.3 Medium 2026-02-25
CVE-2026-25164 OpenEMR's Document and Insurance REST Endpoints Skip ACL — openemr 8.1 High 2026-02-25
CVE-2026-28195 JetBrains TeamCity 安全漏洞 — TeamCity 4.3 Medium 2026-02-25
CVE-2026-28193 JetBrains YouTrack 安全漏洞 — YouTrack 8.8 High 2026-02-25
CVE-2026-26104 Udisks: missing authorization check allows unprivileged users to back up luks headers via udisks d-bus api — Red Hat Enterprise Linux 10 5.5 Medium 2026-02-25
CVE-2026-26103 Udisks: missing authorization check allows unprivileged users to restore luks headers via udisks d-bus api — Red Hat Enterprise Linux 10 7.1 High 2026-02-25
CVE-2026-2301 Post Duplicator <= 3.0.8 - Missing Authorization to Authenticated (Contributor+) Protected Post Meta Insertion via 'customMetaData' Parameter — Post Duplicator 4.3 Medium 2026-02-25
CVE-2026-1916 WPGSI: Spreadsheet Integration <= 3.8.3 - Missing Authorization to Unauthenticated Arbitrary Post Creation and Deletion via Forged Base64 Token — WPGSI: Spreadsheet Integration 7.5 High 2026-02-25
CVE-2026-27608 Parse Dashboard Missing Authorization on Agent Endpoint — parse-dashboard 8.8AI High AI 2026-02-25
CVE-2026-25131 OpenEMR has Broken Access Control in Procedures Configuration — openemr 8.8 High 2026-02-25
CVE-2026-25124 OpenEMR has Broken Access Control in Report/Clients/Message List CSV Export — openemr 6.5 Medium 2026-02-25
CVE-2026-22765 Dell Wyse Management Suite WMS 安全漏洞 — Wyse Management Suite 8.8 High 2026-02-24
CVE-2026-27468 Mastodon may allow unconfirmed FASP to make subscriptions — mastodon 6.7 - 2026-02-24

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