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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8296 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-115373 Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 Authorization Bypass via GET /1.0/operations/{uuid} — incus 6.3 Medium 2026-10-22
CVE-2026-115364 OpenBao before 2.6.3 Missing Header Check on Agent/Proxy Quit Endpoints — openbao 2.2 Low 2026-10-22
CVE-2026-114519 Missing authorization in the Prospero Flow CRM user API allows a basic role user to read and delete other accounts — Prospero Flow CRM 8.6 High 2026-10-22
CVE-2026-113875 SmileCDR HAPI FHIR unauthorized read via subscription — HAPI FHIR 3.1 Low 2026-10-22
CVE-2026-93336 Missing authorization in the unit resources download route in Juju controllers — Juju 7.1 High 2026-10-22
CVE-2026-115502 DataApp links without logging expose job information to other user in KNIME Business Hub — KNIME Business Hub 6.3 Medium 2026-10-22
CVE-2026-114487 Devolutions Server 2026.3.x 及之前版本 PAM 导入越权漏洞 — Server - - 2026-10-22
CVE-2026-114515 OCO-Server: Self-Service Portal uninstall-job authorization bypass — OCO-Server 6.5 Medium 2026-10-22
CVE-2026-112842 WordPress Paid Member Subscriptions plugin <= 3.1.2 - Broken Access Control vulnerability — Paid Member Subscriptions 6.5 Medium 2026-10-22
CVE-2026-115323 EverShop 1.2.2 before 2.2.1 Missing Authorization via Customer Address API — evershop 7.3 High 2026-10-22
CVE-2026-114699 WordPress ЮKassa для WooCommerce plugin <= 2.17.3 - Broken Access Control vulnerability — ЮKassa для WooCommerce 5.3 Medium 2026-10-22
CVE-2026-112218 WordPress Majestic Support plugin <= 1.2.1 - Broken Access Control vulnerability — Majestic Support 5.3 Medium 2026-10-22
CVE-2026-114696 WordPress Page Restriction WordPress (WP) plugin <= 1.6.0 - Broken Access Control vulnerability — Page Restriction WordPress (WP) 5.3 Medium 2026-10-22
CVE-2026-111842 WordPress Sunshine Photo Cart plugin <= 3.7.5 - Broken Access Control vulnerability — Sunshine Photo Cart 5.3 Medium 2026-10-22
CVE-2026-112312 WordPress ACF Extended plugin <= 0.9.2.7 - Broken Access Control vulnerability — ACF Extended 7.5 High 2026-10-22
CVE-2026-110893 WordPress SureDash plugin <= 1.12.2 - Broken Access Control vulnerability — SureDash 5.3 Medium 2026-10-22
CVE-2026-110894 WordPress SureDash plugin <= 1.12.2 - Broken Access Control vulnerability — SureDash 5.3 Medium 2026-10-22
CVE-2026-114182 WordPress PowerPack Addons for Elementor plugin <= 3.1.0 - Broken Access Control vulnerability — PowerPack Addons for Elementor 4.3 Medium 2026-10-22
CVE-2026-112843 WordPress Strong Testimonials plugin <= 3.3.14 - Broken Access Control vulnerability — Strong Testimonials 4.3 Medium 2026-10-22
CVE-2026-112826 WordPress Falcon – WordPress Optimizations & Tweaks plugin <= 2.12.0 - Broken Access Control vulnerability — Falcon – WordPress Optimizations & Tweaks 5.3 Medium 2026-10-22
CVE-2026-114180 WordPress Metform plugin <= 4.3.2 - Broken Access Control vulnerability — Metform 5.3 Medium 2026-10-22
CVE-2026-111847 WordPress MarketKing plugin <= 2.1.72 - Broken Access Control vulnerability — MarketKing 5.4 Medium 2026-10-22
CVE-2026-114175 WordPress eRoom plugin <= 1.7.1 - Settings Change vulnerability — eRoom 5.4 Medium 2026-10-22
CVE-2026-114661 OpenRemote 1.2.0 before 1.31.0 Missing Authorization in Gateway Tunnel Endpoints — openremote 8.5 High 2026-10-22
CVE-2026-84910 Advanced Search - Moderately critical - Access bypass - SA-CONTRIB-2026-118 — Advanced Search - - 2026-10-22
CVE-2026-84912 AI (Artificial Intelligence) - Moderately critical - Access Bypass - SA-CONTRIB-2026-120 — AI (Artificial Intelligence) - - 2026-10-22
CVE-2026-84913 AI translate - Moderately critical - Access Bypass - SA-CONTRIB-2026-121 — AI Translate - - 2026-10-22
CVE-2026-84914 Calculate Working Days - Critical - Access bypass - SA-CONTRIB-2026-122 — Calculate Working Days - - 2026-10-22
CVE-2026-84916 Islandora - Moderately critical - Access bypass - SA-CONTRIB-2026-126 — Islandora - - 2026-10-22
CVE-2026-84921 Webform Submissions Delete - Moderately critical - Access bypass - SA-CONTRIB-2026-133 — Webform Submissions Delete - - 2026-10-22

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