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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6600 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-48168 PraisonAI: GitHub Actions Claude workflow command injection via unquoted PR branch name — PraisonAI 10.0 Critical2026-08-05
CVE-2026-7529 wiseCampaign <= 1.1.16 - Missing Authorization to Unauthenticated Plugin Configuration Modification via REST API — wiseCampaign – WooCommerce Conversions Made Easy 7.5 High2026-08-05
CVE-2026-7456 Udimi Tools <= 3.2 - Missing Authorization to Authenticated (Subscriber+) Plugin Configuration Reset via 'disconnect' AJAX Action — Udimi Tools 6.5 Medium2026-08-05
CVE-2026-71264 WLED Unauthenticated Configuration Disclosure via /json/cfg and Global Settings-PIN Lock State — WLED 8.2 High2026-08-05
CVE-2026-71252 toner-management - Unauthenticated State-Changing Admin Actions — toner-management 8.2 High2026-08-05
CVE-2026-7520 MailChimp Forms by MailMunch <= 3.2.7 - Missing Authorization to Authenticated (Subscriber+) MailMunch Integration Takeover via 'sign_in' AJAX Action — Mailmunch Forms for Mailchimp 8.1 High2026-08-05
CVE-2026-4431 Easy Post Submission <= 2.3.0 - Missing Authorization — Easy Post Submission – Frontend Posting, Guest Publishing & Submit Content for WordPress 9.1 Critical2026-08-05
CVE-2026-54418 Leantime - Missing Authorization on TwoFA JSON-RPC Methods Allows Cross-Account 2FA Secret Disclosure and Bypass — Leantime 8.1 High2026-08-05
CVE-2026-12000 Page and Post Restriction <= 1.4.1 - Unauthenticated Missing Authorization to Sensitive Information Exposure via REST API — Page and Post Restriction 7.5 High2026-08-05
CVE-2026-7105 Xpro Addons <= 1.5.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Creation via get_menu_content_editor() Function — Xpro Addons — 140+ Widgets for Elementor 4.3 Medium2026-08-05
CVE-2026-6079 Material Dashboard <= 1.4.10 - Missing Authorization to Unauthenticated Task Enumeration, Execution, and Deletion — Material Dashboard 7.3 High2026-08-05
CVE-2026-6627 WPFormify <= 1.1.1 - Missing Authorization — WPFormify – Stripe Payments with Form and Checkout 8.2 High2026-08-05
CVE-2026-7726 Layouts for WPBakery <= 1.1.3 - Missing Authorization to Unauthenticated Template Cache Manipulation via 'handle_sync' AJAX Action — Layouts for WPBakery 6.5 Medium2026-08-05
CVE-2026-6639 AI Chatbot & Workflow Automation by AIWU <= 1.4.6 - Missing Authorization to Unauthenticated Sensitive Information Exposure — AI Copilot – Content Generator 7.5 High2026-08-05
CVE-2026-5581 Multi Uploader for Gravity Forms <= 1.1.8 - Missing Authorization to Unauthenticated Arbitrary Media Deletion — Multi Uploader for Gravity Forms 9.1 Critical2026-08-05
CVE-2026-7753 Cost Calculator Builder <= 3.6.17 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure — Cost Calculator Builder 6.5 Medium2026-08-05
CVE-2026-8761 Dokan <= 5.0.2 - Missing Authorization to Authenticated (Vendor+) Privilege Escalation — Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy 8.8 High2026-08-05
CVE-2026-70619 Odysseus Missing Admin Authorization via Embedding Endpoint Routes — odysseus 8.8 High2026-08-04
CVE-2026-70494 Open WebUI: A folder write-collaborator can permanently delete the owner's chats by deleting a shared subfolder — open-webui 8.1 High2026-08-04
CVE-2026-13227 ERPNext v16.25.0 - Improper authorization in Prospect opportunities API — ERPNext 7.1 High2026-08-04
CVE-2026-70487 Open WebUI: Cross-user file content disclosure via request-scoped direct model knowledge metadata — open-webui 5.3 Medium2026-08-04
CVE-2026-70484 Open WebUI: Users denied the image-generation permission can still generate images via chat completions — open-webui 4.3 Medium2026-08-04
CVE-2026-70483 Open WebUI: Any authenticated user can cancel another user's chat generation via the chat delete endpoint — open-webui 3.1 Low2026-08-04
CVE-2026-70475 Flowise: Missing Authorization on Execution Update Endpoint — Flowise 7.1 High2026-08-04
CVE-2026-13229 Zammad 7.0.1 - Improper authorization in ticket article attachment cloning — Zammad 7.1 High2026-08-04
CVE-2026-69252 Flowise: Missing authorization on `/api/v1/files` allows low-privileged API keys to list and delete files across workspaces within the same organization — Flowise 7.2 High2026-08-04
CVE-2026-18650 Missing Authorization Leading to Root Code Execution in HAVELSAN's Liman MYS — Liman MYS 8.8 High2026-08-04
CVE-2026-17070 Vault Credential Confusion via Authorization Bypass in HAVELSAN's Liman MYS — Liman MYS 8.8 High2026-08-04
CVE-2026-63248 Eclipse Milo 授权问题漏洞 — Eclipse Milo 6.9 Medium2026-08-04
CVE-2026-58080 Eclipse Milo 授权问题漏洞 — Eclipse Milo 8.8 High2026-08-04

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