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-39580 WordPress Dashi plugin <= 3.1.8 - Broken Access Control Vulnerability — Dashi 5.8 Medium 2025-04-17
CVE-2025-39583 WordPress BERTHA AI plugin <= 1.12.10.2 - Arbitrary Content Deletion Vulnerability — BERTHA AI 7.1 High 2025-04-17
CVE-2025-26968 WordPress Cloak Front End Email <= 1.9.5 - Broken Access Control Vulnerability — Cloak Front End Email 7.5 High 2025-04-17
CVE-2025-39456 WordPress WP Logger plugin <= 2.2 - Broken Access Control vulnerability — WP Logger 5.4 Medium 2025-04-17
CVE-2025-39457 WordPress Booking and Rental Manager plugin <= 2.2.8 - Broken Access Control vulnerability — Booking and Rental Manager 5.3 Medium 2025-04-17
CVE-2025-31338 Wisdom Master Pro - Missing Authorization — Wisdom Master Pro 5.3AI Medium AI 2025-04-17
CVE-2025-39513 WordPress ActiveDEMAND plugin <= 0.2.46 - Broken Access Control vulnerability — ActiveDEMAND 5.3 Medium 2025-04-16
CVE-2025-39522 WordPress Dynamic Post plugin <= 5.03 - Settings Change vulnerability — Dynamic Post 5.4 Medium 2025-04-16
CVE-2025-39531 WordPress Slazzer Background Changer plugin <= 3.14 - Broken Access Control Vulnerability — Slazzer Background Changer 5.3 Medium 2025-04-16
CVE-2025-39545 WordPress REST API Authentication plugin <= 3.6.3 - Settings Change Vulnerability — WordPress REST API Authentication 5.4 Medium 2025-04-16
CVE-2025-39552 WordPress Zephyr Project Manager plugin <= 3.3.200 - Broken Access Control Vulnerability — Zephyr Project Manager 5.4 Medium 2025-04-16
CVE-2025-39560 WordPress Live Forms plugin <= 4.8.4 - Broken Access Control vulnerability — Live Forms 5.4 Medium 2025-04-16
CVE-2025-39571 WordPress WowStore plugin <= 4.2.4 - Broken Access Control Vulnerability — WowStore 4.3 Medium 2025-04-16
CVE-2025-39591 WordPress WP Subscription Forms plugin <= 1.2.3 - Broken Access Control Vulnerability — WP Subscription Forms 5.4 Medium 2025-04-16
CVE-2025-39602 WordPress WooCommerce Product Table Lite plugin <= 3.9.5 - Broken Access Control vulnerability — WooCommerce Product Table Lite 4.3 Medium 2025-04-16
CVE-2025-30960 WordPress FS Poster plugin <= 6.5.8 - Subscriber+ Site Wide Broken Access Control vulnerability — FS Poster 8.3 High 2025-04-16
CVE-2025-27008 WordPress Unlimited Timeline < 1.6.1 - Broken Access Control Vulnerability — Unlimited Timeline 7.5 High 2025-04-15
CVE-2025-26953 WordPress JetMenu plugin <= 2.4.9 - Broken Access Control Vulnerability — JetMenu 7.5 High 2025-04-15
CVE-2025-26958 WordPress JetBlog plugin <= 2.4.3 - Broken Access Control Vulnerability — JetBlog 7.5 High 2025-04-15
CVE-2025-26959 WordPress Administrator Z <= 2025.03.24 - Privilege Escalation Vulnerability — Administrator Z 8.8 High 2025-04-15
CVE-2025-26955 WordPress Industrial Lite theme <= 1.0.8 - Broken Access Control vulnerability — Industrial Lite 4.3 Medium 2025-04-15
CVE-2025-26942 WordPress JetTricks plugin <= 1.5.1 - Broken Access Control Vulnerability — JetTricks 7.5 High 2025-04-15
CVE-2025-26944 WordPress JetPopup plugin <= 2.0.11 - Broken Access Control Vulnerability — JetPopup 7.5 High 2025-04-15
CVE-2025-26741 WordPress Email Notifications for Updates <= 1.1.6 - Privilege Escalation Vulnerability — Email Notifications for Updates 8.8 High 2025-04-15
CVE-2025-32929 WordPress Barcode Generator for WooCommerce plugin <= 2.0.4 - Arbitrary Content Deletion vulnerability — Barcode Generator for WooCommerce 7.5 High 2025-04-15
CVE-2025-32542 WordPress Eazy Plugin Manager plugin <= 4.3.0 - Broken Access Control vulnerability — Eazy Plugin Manager 8.8 High 2025-04-11
CVE-2025-31041 WordPress AnyTrack Affiliate Link Manager plugin <= 1.0.4 - Broken Access Control Vulnerability — AnyTrack Affiliate Link Manager 7.5 High 2025-04-11
CVE-2025-32260 WordPress DethemeKit For Elementor plugin <= 2.1.10 - Broken Access Control vulnerability — DethemeKit For Elementor 5.3 Medium 2025-04-10
CVE-2025-32240 WordPress Site Notify plugin <= 1.0 - Broken Access Control Vulnerability — Site Notify 6.5 Medium 2025-04-10
CVE-2025-32236 WordPress Woocommerce Products Reorder Drag Drop Multiple Sort plugin <= 1.9 - Broken Access Control vulnerability — Woocommerce Products Reorder Drag Drop Multiple Sort – Sortable, Rearrange Products Vagonic 4.3 Medium 2025-04-10

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