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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8300 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-108615 JeecgBoot through 3.9.5 Missing Authorization via /airag/extData/delete — JeecgBoot 5.4 Medium 2026-10-10
CVE-2026-108613 JeecgBoot through 3.9.5 Missing Authorization via /airag/app/release Endpoint — JeecgBoot 5.4 Medium 2026-10-10
CVE-2026-108612 JeecgBoot through 3.9.5 Missing Authorization via /airag/word/deleteBatch — JeecgBoot 5.4 Medium 2026-10-10
CVE-2026-108611 JeecgBoot through 3.9.5 Missing Authorization via /airag/word/delete Endpoint — JeecgBoot 5.4 Medium 2026-10-10
CVE-2026-108610 JeecgBoot through 3.9.5 Missing Authorization via /airag/word/edit Endpoint — JeecgBoot 4.3 Medium 2026-10-10
CVE-2026-108606 JeecgBoot through 3.9.5 Missing Authorization via /airag/ocr/deleteById — JeecgBoot 5.4 Medium 2026-10-10
CVE-2026-108605 JeecgBoot through 3.9.5 Missing Authorization via /airag/ocr/edit Endpoint — JeecgBoot 4.3 Medium 2026-10-10
CVE-2026-103685 WordPress ALD – Dropshipping and Fulfillment for AliExpress and WooCommerce plugin <= 2.2.4 - Broken Access Control vulnerability — ALD – Dropshipping and Fulfillment for AliExpress and WooCommerce 4.3 Medium 2026-10-10
CVE-2026-65459 WordPress Forminator plugin <= 1.57.3 - Arbitrary Content Deletion vulnerability — Forminator 7.5 High 2026-10-10
CVE-2026-62118 WordPress Barcode Scanner with Inventory & Order Manager plugin <= 1.13.1 - Broken Access Control vulnerability — Barcode Scanner with Inventory & Order Manager 7.3 High 2026-10-10
CVE-2026-62035 WordPress AWS S3 for WordPress Plugin – Upcasted plugin <= 3.1.0 - Broken Access Control vulnerability — AWS S3 for WordPress Plugin – Upcasted 6.3 Medium 2026-10-10
CVE-2026-62033 WordPress uListing plugin <= 2.2.0 - Settings Change vulnerability — uListing 7.6 High 2026-10-10
CVE-2026-42706 WordPress DK theme <= 3.2.1 - Broken Access Control vulnerability — DK 7.5 High 2026-10-10
CVE-2026-42705 WordPress Grand News theme <= 3.4 - Broken Access Control vulnerability — Grand News 7.5 High 2026-10-10
CVE-2026-40808 WordPress Jetpack VideoPress plugin <= 3.6 - Broken Access Control vulnerability — Jetpack VideoPress 6.5 Medium 2026-10-10
CVE-2026-40802 WordPress Pubjet | پاب‌جت plugin <= 5.4.8 - Settings Change vulnerability — Pubjet | پاب‌جت 7.6 High 2026-10-10
CVE-2026-40801 WordPress Wordable plugin <= 8.2.10 - Broken Access Control vulnerability — Wordable 8.1 High 2026-10-10
CVE-2026-40777 WordPress WPSection plugin <= 1.5.1 - Broken Access Control vulnerability — WPSection 8.1 High 2026-10-10
CVE-2026-103357 WordPress GIFT4U plugin <= 1.1.3 - Broken Access Control vulnerability — GIFT4U 6.9 Medium 2026-10-10
CVE-2026-106609 WordPress Bayarcash WooCommerce plugin <= 4.4.2 - Broken Access Control vulnerability — Bayarcash WooCommerce 7.5 High 2026-10-10
CVE-2026-108581 Octop through 1.0.2b6 Missing Authorization Exposes Provider API Keys via /api/providers — Octop 6.5 Medium 2026-10-10
CVE-2026-108165 Immich through 3.3.1 Missing Authorization in Partner Sync Exposes Locked Folder Metadata — immich 4.3 Medium 2026-10-10
CVE-2026-104728 AutomatorWP <= 5.8.4 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via wp_ajax_automatorwp_fluentform_get_forms AJAX Action — AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI 4.3 Medium 2026-10-10
CVE-2026-93950 WordPress Motors theme <= 1.4.108 - Broken Access Control vulnerability — Motors 7.5 High 2026-10-10
CVE-2026-3717 CV Builder – Professional Resume Builder SaaS <= 1.3.1 - Missing Authorization to Unauthenticated PNG File Upload — WP CV Builder 5.3 Medium 2026-10-10
CVE-2026-94538 WP File Download <= 6.3.9 - Missing Authorization to Authenticated (Subscriber+) Arbitrary File Deletion/Modification via 'task' Parameter to Multiple Functions — WP File Download 8.1 High 2026-10-10
CVE-2026-15178 Fluent Forms <= 6.2.5 - Missing Authorization to Authenticated (Custom+) Sensitive Data Exposure and Modification — Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder 5.4 Medium 2026-10-10
CVE-2026-104742 AI Puffer <= 2.4.89 - Missing Authorization to Authenticated (Subscriber+) Semantic Search Settings Modification via ajax_save_semantic_search_settings AJAX action — AI Puffer – AI Chatbot, AI Writer & Automation 3.1 Low 2026-10-10
CVE-2026-104741 AI Puffer <= 2.4.89 - Missing Authorization to Authenticated (Subscriber+) Global Plugin Settings Modification via ajax_save_cpt_indexing_options AJAX Endpoint — AI Puffer – AI Chatbot, AI Writer & Automation 3.1 Low 2026-10-10
CVE-2026-89301 rtMedia for WordPress, BuddyPress and bbPress <= 4.7.13 - Missing Authorization to Unauthenticated Limited File Read/Disclosure and Limited File Deletion via Sideload via 'files[tmp_name]' Parameter — rtMedia for WordPress, BuddyPress and bbPress 7.5 High 2026-10-10

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