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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6923 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-2025-2276 Ultimate Dashboard <= 3.8.7 - Missing Authorization to Authenticated (Subscriber+) Plugin Modules Activation/Deactivation — Ultimate Dashboard – Custom WordPress Dashboard 4.3 Medium 2025-03-25
CVE-2025-2224 Directorist <= 8.2 - Missing Authorization to Unauthenticated Arbitrary Post Publishing — Directorist: AI-Powered Business Directory, Listings & Classified Ads 5.3 Medium 2025-03-25
CVE-2025-30605 WordPress sourceplay-navermap plugin <= 0.0.2 - Broken Access Control vulnerability — sourceplay-navermap 4.3 Medium 2025-03-24
CVE-2025-30592 WordPress Advanced Dewplayer - plugin <= 1.6 Broken Access Control Vulnerability — Advanced Dewplayer 5.3 Medium 2025-03-24
CVE-2025-30591 WordPress Music Press Pro plugin <= 1.4.6 Broken Access Control Vulnerability — Music Press Pro 5.3 Medium 2025-03-24
CVE-2025-30581 WordPress Top Bar plugin <= 3.3 - Broken Access Control Vulnerability — Top Bar 5.3 Medium 2025-03-24
CVE-2025-30543 WordPress Menu Duplicator plugin <= 1.0 - Broken Access Control vulnerability — Menu Duplicator 4.3 Medium 2025-03-24
CVE-2025-1408 ProfileGrid – User Profiles, Groups and Communities <= 5.9.4.4 - Missing Authorinzation to Authenticated (Subscriber+) Join Group Requests Management — ProfileGrid – User Profiles, Groups and Communities 4.3 Medium 2025-03-22
CVE-2024-13737 Motors – Car Dealer, Classifieds & Listing <= 1.4.57 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Deletion and Listing Template Creation — Motors – Car Dealership & Classified Listings Plugin 4.3 Medium 2025-03-22
CVE-2024-7767 Improper Access Control in danswer-ai/danswer — danswer-ai/danswer 8.3 - 2025-03-20
CVE-2024-10272 Broken Access Control in lunary-ai/lunary — lunary-ai/lunary 7.5 - 2025-03-20
CVE-2024-7043 Improper Access Control in open-webui/open-webui — open-webui/open-webui 9.8 - 2025-03-20
CVE-2024-10330 Improper Access Control in lunary-ai/lunary — lunary-ai/lunary 4.3 - 2025-03-20
CVE-2024-10363 Improper Access Control in danny-avila/LibreChat — danny-avila/librechat 7.5 - 2025-03-20
CVE-2024-9096 Improper Authorization in lunary-ai/lunary — lunary-ai/lunary 4.3 - 2025-03-20
CVE-2024-10762 Missing Authorization in lunary-ai/lunary — lunary-ai/lunary 5.4 - 2025-03-20
CVE-2024-9000 Improper Authorization and Duplicate Slug Vulnerability in lunary-ai/lunary — lunary-ai/lunary 6.5 - 2025-03-20
CVE-2024-2292 Access Control Vulnerabilities lead to Violation of Privacy and Modification of Personal Data — changeweb/unifiedtransform 8.1 - 2025-03-20
CVE-2024-10274 Improper Authorization in lunary-ai/lunary — lunary-ai/lunary 4.3 - 2025-03-20
CVE-2024-8999 Improper Access Control in lunary-ai/lunary — lunary-ai/lunary 5.3 - 2025-03-20
CVE-2024-9095 Improper Authorization in lunary-ai/lunary — lunary-ai/lunary 8.1 - 2025-03-20
CVE-2024-13060 Improper Authorization in mintplex-labs/anything-llm — mintplex-labs/anything-llm 4.3 - 2025-03-20
CVE-2025-1766 Event Manager, Events Calendar, Tickets, Registrations – Eventin <= 4.0.24 - Missing Authorization to Unauthenticated Payment Status Update — Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered) 5.3 Medium 2025-03-20
CVE-2024-12920 FoodBakery | Delivery Restaurant Directory WordPress Theme <= 4.7 - Missing Authorization in Multiple Functions — FoodBakery | Delivery Restaurant Directory WordPress Theme 8.8 High 2025-03-19
CVE-2024-13412 CozyStay <= 1.7.0 - Missing Authorization to Arbitrary Action Execution in ajax_handler — CozyStay - Hotel Booking WordPress Theme 7.5 High 2025-03-19
CVE-2024-12922 Altair <= 5.2.4 - Unauthenticated Arbitrary Options Update via pp_import_current — Altair 9.8 Critical 2025-03-19
CVE-2025-2290 LifterLMS <= 8.0.1 - Missing Authorization to Unauthenticated Post Trashing — LifterLMS – WP LMS for eLearning, Online Courses, & Quizzes 5.3 Medium 2025-03-19
CVE-2025-2262 Logo Slider <= 3.7.3 - Unauthenticated Arbitrary Shortcode Execution — Logo Slider – Logo Showcase, Logo Carousel, Logo Gallery and Client Logo Presentation 7.3 High 2025-03-18
CVE-2025-26961 WordPress Fresh Framework plugin <= 1.70.0 - Unauthenticated Broken Access Control vulnerability — Fresh Framework 8.6 High 2025-03-15
CVE-2025-26969 WordPress PrivateContent plugin <= 8.11.5 - Subscriber+ Site Wide Broken Access Control vulnerability — PrivateContent 8.3 High 2025-03-15

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