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

Goal: 1000 CNY · Raised: 1020 CNY

100%

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

5676 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-21836 HCL DominoIQ is affected by broken access control — DominoIQ 6.5 Medium2026-05-20
CVE-2026-27405 WordPress WpBookingly plugin <= 1.2.9 - Broken Access Control vulnerability — WpBookingly 6.5 Medium2026-05-20
CVE-2026-27424 WordPress Image Photo Gallery Final Tiles Grid plugin <= 3.6.11 - Broken Access Control vulnerability — Image Photo Gallery Final Tiles Grid 4.3 Medium2026-05-20
CVE-2026-45443 WordPress PDF for Elementor Forms + Drag And Drop Template Builder plugin <= 5.5.1 - Broken Access Control vulnerability — PDF for Elementor Forms + Drag And Drop Template Builder 5.0 Medium2026-05-20
CVE-2026-5200 AcyMailing <= 10.8.2 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation via 'acymailing_router' — AcyMailing – An Ultimate Newsletter Plugin and Marketing Automation Solution for WordPress 8.8 High2026-05-20
CVE-2026-44392 Movable Type权限绕过漏洞 — Movable Type--2026-05-20
CVE-2025-15369 Xpro Addons — 140+ Widgets for Elementor <= 1.5.0 - Missing Authorization to Unauthenticated Xpro Template Creation — Xpro Addons — 140+ Widgets for Elementor 5.3 Medium2026-05-20
CVE-2026-8610 TypeSquare Webfonts for ConoHa <= 2.0.4 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Modification via 'fontThemeUseType' Parameter — TypeSquare Webfonts for ConoHa 4.3 Medium2026-05-20
CVE-2026-8495 Date iCal - Critical - Information disclosure - SA-CONTRIB-2026-037 — Date iCal--2026-05-19
CVE-2026-34154 Discourse has a subscription access bypass in its discourse-subscriptions plugin — discourse--2026-05-19
CVE-2026-8096 Kirki <= 6.0.6 - Missing Authorization to Authenticated (Subscriber+) Sensitive Form Submission Data Exposure via 'kirki_wp_admin_get_apis' Action — Kirki – Freeform Page Builder, Website Builder & Customizer 6.5 Medium2026-05-19
CVE-2026-47100 Funnel Builder for WooCommerce Checkout < 3.15.0.3 Missing Authorization via AJAX — Funnel Builder for WooCommerce Checkout 7.5 High2026-05-19
CVE-2026-45442 WordPress Presto Player plugin <= 4.1.3 - Broken Access Control vulnerability — Presto Player 4.3 Medium2026-05-19
CVE-2026-33514 Discourse: Information Disclosure in Form Template API Due to Missing Authorization — discourse--2026-05-19
CVE-2026-32312 GLPI: Unauthorized export of form structure — glpi--2026-05-18
CVE-2026-30950 AutoGPT has Authenticated Session Hijacking via IDOR — AutoGPT 7.1 High2026-05-18
CVE-2026-45244 Summarize < 0.15.1 Unapproved Browser Automation Execution — summarize 5.4 Medium2026-05-18
CVE-2026-45242 Summarize < 0.15.1 Path Traversal via slidesDir Parameter — summarize 7.1 High2026-05-18
CVE-2026-45243 Summarize < 0.15.1 Browser Extension Missing Authorization via Content Script — summarize 6.1 Medium2026-05-18
CVE-2026-5163 Missing authorization check in AI message rewrite endpoint allows access to private thread content — Mattermost 6.5 Medium2026-05-18
CVE-2026-3117 Instance and webhook GitLab plugin commands were able to be run by non-admin users — Mattermost 6.5 Medium2026-05-18
CVE-2026-3637 Mattermost fails to enforce create_post permission when editing posts — Mattermost 4.3 Medium2026-05-18
CVE-2025-4202 Multicollab: Content Team Collaboration and Editorial Workflow <= 5.2 - Missing Authorization to Authenticated (Subscriber+) Collaboration Comment — Multicollab: Content Team Collaboration and Editorial Workflow 4.3 Medium2026-05-16
CVE-2026-8681 Essential Chat Support <= 1.0.1 - Missing Authorization to Unauthenticated Settings Reset via 'ecs_reset_settings' Parameter — Essential Chat Support 5.3 Medium2026-05-16
CVE-2026-45667 Open WebUI: Unauthenticated endpoint can trigger embedding generation (cost/DoS) — open-webui 6.5 Medium2026-05-15
CVE-2026-44571 Open WebUI: Improper Authorization in Standard Channels Allows Message Updates with Read Permission — open-webui 6.5 Medium2026-05-15
CVE-2026-45350 Open WebUI: Chat completion API allows tool restrictions to be bypassed — open-webui 7.1 High2026-05-15
CVE-2026-44569 Open WebUI: Insecure Message Access Breaks Authorization — open-webui 7.1 High2026-05-15
CVE-2026-44550 Open WebUI: Mass Assignment via Pydantic extra='allow' Allows Creating Folders in Other Users' Accounts — open-webui 5.0 Medium2026-05-15
CVE-2026-44554 Open WebUI: Knowledge Base Destruction and RAG Poisoning via Unauthorized Collection Overwrite — open-webui 8.1 High2026-05-15

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