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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

5660 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-62874 WordPress AnyComment plugin <= 0.3.6 - Broken Access Control vulnerability — AnyComment 4.3 Medium2025-12-31
CVE-2025-62099 WordPress Signature Add-On for Gravity Forms plugin <= 1.8.6 - Broken Access Control vulnerability — Signature Add-On for Gravity Forms 4.3 Medium2025-12-31
CVE-2025-63038 WordPress WP Custom Admin Interface plugin <= 7.40 - Broken Access Control vulnerability — WP Custom Admin Interface 4.3 Medium2025-12-31
CVE-2025-62078 WordPress Easy Upload Files During Checkout plugin <= 3.0.0 - Broken Access Control vulnerability — Easy Upload Files During Checkout 4.3 Medium2025-12-31
CVE-2025-49339 WordPress Direct Payments WP plugin <= 1.3.2 - Broken Access Control vulnerability — Direct Payments WP 4.3 Medium2025-12-31
CVE-2025-62115 WordPress Hide Plugins plugin <= 1.0.4 - Broken Access Control vulnerability — Hide Plugins 4.3 Medium2025-12-31
CVE-2025-62087 WordPress Sticky Notes for WP Dashboard plugin <= 1.2.4 - Broken Access Control vulnerability — Sticky Notes for WP Dashboard 4.3 Medium2025-12-31
CVE-2025-49356 WordPress Orders Chat for WooCommerce plugin <= 1.2.0 - Broken Access Control vulnerability — Orders Chat for WooCommerce 4.3 Medium2025-12-31
CVE-2025-63004 WordPress All in One Accessibility plugin <= 1.15 - Broken Access Control vulnerability — All in One Accessibility 4.3 Medium2025-12-31
CVE-2025-62130 WordPress Accordion Slider Gallery plugin <= 2.7 - Broken Access Control vulnerability — Accordion Slider Gallery 4.3 Medium2025-12-31
CVE-2025-62131 WordPress Tasty Recipes Lite plugin <= 1.1.5 - Broken Access Control vulnerability — Tasty Recipes Lite 4.3 Medium2025-12-31
CVE-2025-62132 WordPress Tasty Recipes Lite plugin <= 1.1.5 - Broken Access Control vulnerability — Tasty Recipes Lite 4.3 Medium2025-12-31
CVE-2025-62751 WordPress Vireo theme <= 1.0.24 - Broken Access Control vulnerability — Vireo 4.3 Medium2025-12-31
CVE-2025-62150 WordPress History Timeline plugin <= 1.0.6 - Broken Access Control vulnerability — History Timeline 4.3 Medium2025-12-31
CVE-2025-62154 WordPress AI Content Writing Assistant (Content Writer, ChatGPT, Image Generator) All in One plugin <= 1.1.7 - Broken Access Control vulnerability — AI Content Writing Assistant (Content Writer, ChatGPT, Image Generator) All in One 4.3 Medium2025-12-31
CVE-2025-62116 WordPress AI Copilot plugin <= 1.5.2 - Broken Access Control vulnerability — AI Copilot 5.3 Medium2025-12-31
CVE-2025-62122 WordPress Trash Duplicate and 301 Redirect plugin <= 1.9.1 - Broken Access Control vulnerability — Trash Duplicate and 301 Redirect 5.3 Medium2025-12-31
CVE-2025-62079 WordPress WP Export Categories & Taxonomies plugin <= 1.0.3 - Broken Access Control vulnerability — WP Export Categories & Taxonomies 5.3 Medium2025-12-31
CVE-2025-49338 WordPress Flowbox plugin <= 1.1.6 - Broken Access Control vulnerability — Flowbox 5.3 Medium2025-12-31
CVE-2025-62747 WordPress Featured Image Generator plugin <= 1.3.4 - Broken Access Control vulnerability — Featured Image Generator 5.3 Medium2025-12-31
CVE-2025-15390 PHPGurukul Small CRM edit-user.php authorization — Small CRM 6.3 Medium2025-12-31
CVE-2025-62129 WordPress RestroPress plugin <= 3.2.7 - Broken Access Control vulnerability — RestroPress 5.3 Medium2025-12-31
CVE-2025-62092 WordPress Wiremo plugin <= 1.4.99 - Broken Access Control vulnerability — Wiremo 5.3 Medium2025-12-31
CVE-2025-62755 WordPress GS Portfolio for Envato plugin <= 1.4.2 - Broken Access Control vulnerability — GS Portfolio for Envato 5.3 Medium2025-12-31
CVE-2025-63031 WordPress EasyTest plugin <= 1.0.1 - Broken Access Control vulnerability — EasyTest 5.3 Medium2025-12-31
CVE-2025-62141 WordPress Wawp plugin <= 4.4 - Broken Access Control vulnerability — Wawp 5.3 Medium2025-12-31
CVE-2025-63022 WordPress Simple Like Page plugin <= 1.5.3 - Broken Access Control vulnerability — Simple Like Page 5.3 Medium2025-12-31
CVE-2025-63016 WordPress QuadLayers TikTok Feed plugin <= 4.6.5 - Broken Access Control vulnerability — QuadLayers TikTok Feed 5.3 Medium2025-12-31
CVE-2025-62145 WordPress DMCA Protection Badge plugin <= 2.2.0 - Broken Access Control vulnerability — DMCA Protection Badge 5.3 Medium2025-12-31
CVE-2025-62147 WordPress Realbig plugin <= 1.1.3 - Broken Access Control vulnerability — Realbig 5.3 Medium2025-12-31

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