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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

5967 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-2025-46519 WordPress Media Library Downloader plugin <= 1.3.1 - Broken Access Control Vulnerability — Media Library Downloader 4.3 Medium2025-04-24
CVE-2025-46489 WordPress Bulk Assign Linked Products For WooCommerce plugin <= 2.1 - Broken Access Control Vulnerability — Bulk Assign Linked Products For WooCommerce 5.3 Medium2025-04-24
CVE-2025-46485 WordPress WP Customize Login Page plugin <= 1.6.5 - Broken Access Control Vulnerability — WP Customize Login Page 5.3 Medium2025-04-24
CVE-2025-46470 WordPress Smart Hashtags [#hashtagger] plugin <= 7.2.3 - Broken Access Control Vulnerability — Smart Hashtags [#hashtagger] 4.3 Medium2025-04-24
CVE-2025-39385 WordPress Sirat theme <= 1.5.1 - Broken Access Control vulnerability — Sirat 4.3 Medium2025-04-24
CVE-2025-39390 WordPress Booking and Rental Manager plugin <= 2.3.6 - Broken Access Control vulnerability — Booking and Rental Manager 5.3 Medium2025-04-24
CVE-2021-47662 Unauthenticated remote shutdown of the cobot — Franka Emika Robot 7.5 High2025-04-24
CVE-2024-13307 Reales WP - Real Estate WordPress Theme <= 2.1.2 - Missing Authorization to Unauthenticated Attachment Deletion and Favorite Property Updates — Reales WP - Real Estate WordPress Theme 5.3 Medium2025-04-24
CVE-2025-3604 Flynax Bridge <= 2.2.0 - Unauthenticated Privilege Escalation via Account Takeover — Flynax Bridge 9.8 Critical2025-04-24
CVE-2025-3058 Xelion Webchat <= 9.1.0 - Authenticated (Subscriber+) Arbitrary Options Update — Xelion Webchat 8.8 High2025-04-24
CVE-2024-12244 Missing Authorization in GitLab — GitLab 4.3 Medium2025-04-24
CVE-2025-1021 Synology DiskStation Manager 安全漏洞 — DiskStation Manager (DSM) 7.5 High2025-04-23
CVE-2025-46247 WordPress Appointment Booking Calendar plugin <= 1.3.92 - Broken Access Control Vulnerability — Appointment Booking Calendar 5.3 Medium2025-04-22
CVE-2025-46244 WordPress Advanced Linked Variations for Woocommerce plugin <= 1.0.3 - Broken Access Control Vulnerability — Advanced Linked Variations for Woocommerce 5.3 Medium2025-04-22
CVE-2025-46232 WordPress Download Alt Text AI plugin <= 1.9.93 - Broken Access Control Vulnerability — Download Alt Text AI 4.3 Medium2025-04-22
CVE-2025-2298 Authenticated API Endpoint Allows Arbitrary File Deletion in Dremio Software — Dremio Software 9.6 -2025-04-21
CVE-2025-3124 Missing Authorization vulnerability was identified in GitHub Enterprise Server that allowed unauthorized access to private repository names — Enterprise Server 4.3AIMediumAI2025-04-17
CVE-2025-23773 WordPress Delete All Posts plugin <= 1.1.1 - Broken Access Control vulnerability — Delete All Posts 6.5 Medium2025-04-17
CVE-2025-23906 WordPress WordPress Dashboard Tweeter plugin <= 1.3.2 - Settings Change vulnerability — WordPress Dashboard Tweeter 6.5 Medium2025-04-17
CVE-2025-23958 WordPress Editor Wysiwyg Background Color plugin <= 1.0 - Broken Access Control vulnerability — Editor Wysiwyg Background Color 6.5 Medium2025-04-17
CVE-2025-24577 WordPress Poll Maker plugin <= 5.5.0 - Broken Access Control vulnerability — Poll Maker 6.5 Medium2025-04-17
CVE-2025-24581 WordPress Instantio plugin <= 3.3.7 - Settings Change vulnerability — Instantio 6.5 Medium2025-04-17
CVE-2025-24583 WordPress 12 Step Meeting List plugin <= 3.16.5 - Settings Change vulnerability — 12 Step Meeting List 6.5 Medium2025-04-17
CVE-2025-24737 WordPress WP Helper Premium plugin <= 4.6.1 - Broken Access Control vulnerability — WP Helper Premium 6.5 Medium2025-04-17
CVE-2025-27310 WordPress Page and Post Lister plugin <= 1.2.1 - Arbitrary Content Deletion vulnerability — Page and Post Lister 6.5 Medium2025-04-17
CVE-2025-32544 WordPress WooCommerce Loyal Customers plugin <= 2.6 - Broken Access Control vulnerability — WooCommerce Loyal Customers 7.5 High2025-04-17
CVE-2025-32593 WordPress Add Product Frontend for WooCommerce plugin <= 1.0.8 - Arbitrary Content Deletion vulnerability — Add Product Frontend for WooCommerce 8.2 High2025-04-17
CVE-2025-32620 WordPress Doppler Forms plugin <= 2.4.6 - Broken Access Control vulnerability — Doppler Forms 7.1 High2025-04-17
CVE-2025-39532 WordPress Spice Blocks plugin <= 2.0.7.7 - Broken Access Control vulnerability — Spice Blocks 7.5 High2025-04-17
CVE-2025-39533 WordPress Starfish Review Generation & Marketing plugin <= 3.1.19 - Privilege Escalation vulnerability — Starfish Review Generation & Marketing 8.8 High2025-04-17

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