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-26375 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 8.8 High 2025-02-12
CVE-2025-26374 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 6.5 Medium 2025-02-12
CVE-2025-26373 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 6.5 Medium 2025-02-12
CVE-2025-26372 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 7.1 High 2025-02-12
CVE-2025-26371 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 8.8 High 2025-02-12
CVE-2025-26370 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 7.1 High 2025-02-12
CVE-2025-26369 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 8.8 High 2025-02-12
CVE-2025-26368 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 8.1 High 2025-02-12
CVE-2025-26367 Q-Free MAXTIME Suite 安全漏洞 — MaxTime 4.3 Medium 2025-02-12
CVE-2024-12296 Apus Framework <= 2.4 - Authenticated (Subscriber+) Arbitrary Options Update in import_page_options — Apus Framework 8.8 High 2025-02-12
CVE-2024-13374 WP Table Manager <= 4.1.3 - Missing Authorization to Authenticated (Subscriber+) Directory Traversal to Folder/File Name Disclosure — WP Table Manager 4.3 Medium 2025-02-12
CVE-2024-13656 Click Mag - Viral WordPress News Magazine/Blog Theme <= 3.6.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Options Deletion — Click Mag - Viral WordPress News Magazine/Blog Theme 8.1 High 2025-02-12
CVE-2024-13654 ZoxPress - The All-In-One WordPress News Theme <= 2.12.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Options Deletion — ZoxPress - The All-In-One WordPress News Theme 8.1 High 2025-02-12
CVE-2024-13653 ZoxPress - The All-In-One WordPress News Theme <= 2.12.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Options Update — ZoxPress - The All-In-One WordPress News Theme 8.8 High 2025-02-12
CVE-2024-12164 WPSyncSheets Lite For WPForms – WPForms Google Spreadsheet Addon <= 1.6 - Missing Authorization to Authenticated (Subscriber+) Settings Reset — WPSyncSheets For WPForms – Google Sheets Connector for WPForms & Real‑Time Data Export 4.3 Medium 2025-02-12
CVE-2024-13800 Popup Plugin For WordPress - ConvertPlus <= 3.5.30 - Missing Authorization to Authenticated (Subscriber+) Limited Options Update — ConvertPlus 8.1 High 2025-02-12
CVE-2024-13769 Puzzles | WP Magazine / Review with Store WordPress Theme + RTL <= 4.2.4 - Missing Authorization to Authenticated (Subscriber+) Stored Cross-Site Scripting — Puzzles | WP Magazine / Review with Store WordPress Theme + RTL 6.4 Medium 2025-02-12
CVE-2024-13541 aDirectory – WordPress Directory Listing Plugin <= 2.3 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Deletion — aDirectory – WP Business Directory Plugin and Classified Ads Listings Directory 4.3 Medium 2025-02-12
CVE-2024-13554 The Ultimate WordPress Toolkit – WP Extended <= 3.0.13 - Missing Authorization to Unauthenticated Post Order Manipulation — The Ultimate WordPress Toolkit – WP Extended 5.3 Medium 2025-02-12
CVE-2024-13643 Zox News <= 3.17.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Options Modification — Zox News - Professional WordPress News & Magazine Theme 8.8 High 2025-02-11
CVE-2025-25241 Missing Authorization check in SAP Fiori Apps Reference Library (My Overtime Requests) — SAP Fiori Apps Reference Library (My Overtime Requests) 5.4 Medium 2025-02-11
CVE-2025-23190 Missing Authorization check in SAP NetWeaver and ABAP platform (ST-PI) — SAP NetWeaver and ABAP platform (ST-PI) 4.3 Medium 2025-02-11
CVE-2025-23189 Missing Authorization Check in SAP NetWeaver and ABAP Platform (SDCCN) — SAP NetWeaver and ABAP Platform (SDCCN) 4.3 Medium 2025-02-11
CVE-2025-23187 Missing Authorization Check in SAP NetWeaver and ABAP Platform (SDCCN) — SAP NetWeaver and ABAP Platform (SDCCN) 5.3 Medium 2025-02-11
CVE-2025-25167 WordPress BookPress – For Book Authors Plugin <= 1.2.7 - Broken Access Control vulnerability — BookPress – For Book Authors 8.2 High 2025-02-07
CVE-2025-25120 WordPress Slide Banners plugin <= 1.3 - Broken Access Control vulnerability — Slide Banners 4.3 Medium 2025-02-07
CVE-2025-25110 WordPress Event Kikfyre plugin <= 2.1.8 - Broken Access Control vulnerability — Event Kikfyre 5.4 Medium 2025-02-07
CVE-2025-25081 WordPress Embed RSS plugin <= 3.1 - Arbitrary Shortcode Execution vulnerability — Embed RSS 4.8 Medium 2025-02-07
CVE-2024-3976 Missing Authorization in GitLab — GitLab 6.5 Medium 2025-02-05
CVE-2024-1539 Missing Authorization in GitLab — GitLab 4.3 Medium 2025-02-05

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