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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6713 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-69146 MLflow: LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth — mlflow 6.5 Medium2026-08-17
CVE-2026-69148 MLflow: CreateModelVersion source validation does not check READ permission on referenced run_id — mlflow 7.1 High2026-08-17
CVE-2026-75108 Next Terminal Missing Per-Asset Authorization on Portal Endpoints — next-terminal 5.4 Medium2026-08-17
CVE-2026-75109 Determined Missing Authorization Check on Generic Task Endpoints — determined 7.1 High2026-08-17
CVE-2026-54356 Budibase authenticated arbitrary S3 signed upload URL issuance via `/api/attachments/:datasourceId/url` — budibase 7.1 High2026-08-17
CVE-2026-64866 New API: Admin can reset passkeys for same-level or higher-privileged users — new-api 5.1 Medium2026-08-17
CVE-2026-75051 YouTrack 2026.2.17917前项目未授权转移漏洞 — YouTrack 8.1 High2026-08-17
CVE-2026-75049 JetBrains YouTrack多版本越权读取受限文章 — YouTrack 6.5 Medium2026-08-17
CVE-2026-75046 YouTrack<2026.2账号枚举漏洞 — YouTrack 4.3 Medium2026-08-17
CVE-2026-75044 JetBrains YouTrack任意实体删除漏洞 — YouTrack 8.1 High2026-08-17
CVE-2026-53960 Discourse: Hidden first-post excerpt is emitted in Q&A schema JSON-LD — discourse 5.3 Medium2026-08-17
CVE-2026-55704 Discourse: Shared-draft titles and excerpts leak through group post serialization — discourse 4.3 Medium2026-08-17
CVE-2026-59829 Discourse: Review queue exposes flag-related private message excerpts to category group moderators — discourse 4.3 Medium2026-08-17
CVE-2026-16049 _GitLab Plugin allows cross-channel post injection and phishing via missing channel permission checks in issue API endpoints_ — Mattermost 3.9 Medium2026-08-17
CVE-2026-16047 Board channel linking without read channel permission validation — Mattermost 4.3 Medium2026-08-17
CVE-2026-16471 Broken Access Control in Dolusoft Software's Sonlogger — Sonlogger 7.5 High2026-08-17
CVE-2026-16467 Broken Access Control in Dolusoft Software's Fortilogger — Fortilogger 7.5 High2026-08-17
CVE-2026-74869 stoatchat before 0.15.0 Missing Authorization via Subscribe — stoatchat 7.7 High2026-08-17
CVE-2026-18347 Kirki <= 6.1.1 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via 'context' Parameter — Kirki – Freeform Page Builder, Website Builder & Customizer 4.3 Medium2026-08-16
CVE-2026-17087 WP Travel Engine <= 6.8.4 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'booking_id' Parameter — WP Travel Engine – Tour Booking Plugin – Tour Operator Software 7.5 High2026-08-16
CVE-2026-15345 ShortPixel Adaptive Images <= 3.11.5 - Missing Authorization to Authenticated (Subscriber+) Third-Party Plugin Option Modification via 'causer' Parameter — ShortPixel Adaptive Images – WebP, AVIF, CDN, Image Optimization 4.3 Medium2026-08-16
CVE-2026-18316 Solace Extra <= 1.6.0 - Missing Authorization to Unauthenticated Site Content Deletion and Unauthorized Demo Import via action-import-zip AJAX Action — Solace Extra 9.1 Critical2026-08-16
CVE-2026-16779 Kubio AI Page Builder <= 2.8.5 - Missing Authorization to Authenticated (Contributor+) Front-Page/Menu/Template Configuration Reversion via kubio_restore_front_page AJAX Action — Kubio AI Page Builder 4.3 Medium2026-08-16
CVE-2026-13167 Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI <= 3.5.2 - Missing Authorization to Authenticated (Delegated+) Arbitrary Plugin Activation via REST API and AJAX Endpoints — Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI 4.3 Medium2026-08-16
CVE-2026-8840 Booking calendar, Appointment Booking System <= 3.2.36 - Missing Authorization to Unauthenticated Arbitrary Modification via wpdevart_payment AJAX Action — Booking calendar, Appointment Booking System 5.3 Medium2026-08-15
CVE-2026-73048 SiYuan before v3.7.4 Information Disclosure via getRefIDsByFileAnnotationID — siyuan 5.8 Medium2026-08-14
CVE-2026-72825 Grav before 1.0.13 API-key scope cap bypass via ReportsController — grav 7.6 High2026-08-14
CVE-2026-72824 Grav before 1.0.13 API Key Scope Bypass via PagesController — grav 9.8 Critical2026-08-14
CVE-2026-72823 Grav before 1.0.13 API-key scope cap bypass via DemoController — grav 5.4 Medium2026-08-14
CVE-2026-72812 SiYuan before v3.7.4 Missing Authorization via refreshBacklink — siyuan 6.5 Medium2026-08-14

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