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-31799 WordPress Publitio plugin <= 2.1.8 - Broken Access Control vulnerability — Publitio 4.3 Medium2025-04-01
CVE-2025-31798 WordPress Publitio Plugin <= 2.1.8 - Broken Access Control vulnerability — Publitio 4.3 Medium2025-04-01
CVE-2025-31791 WordPress Pin Generator Plugin <= 2.0.0 - Broken Access Control vulnerability — Pin Generator 5.4 Medium2025-04-01
CVE-2025-31786 WordPress Simple Icons plugin <= 2.8.4 - Broken Access Control vulnerability — Simple Icons 5.3 Medium2025-04-01
CVE-2025-31787 WordPress Cue by AudioTheme.com plugin <= 2.4.4 - Broken Access Control vulnerability — Cue 4.3 Medium2025-04-01
CVE-2025-31782 WordPress mb.YTPlayer plugin <= 3.3.8 - Broken Access Control vulnerability — mb.YTPlayer 5.4 Medium2025-04-01
CVE-2025-31780 WordPress Append Content plugin <= 2.1.1 - CSRF to Settings Change vulnerability — Append Content 6.5 Medium2025-04-01
CVE-2025-31781 WordPress Gift Cards for WooCommerce plugin <= 1.5.8 - Broken Access Control vulnerability — Gift Cards for WooCommerce 4.3 Medium2025-04-01
CVE-2025-31777 WordPress Clockinator Lite plugin <= 1.0.9 - Broken Access Control vulnerability — Clockinator Lite 5.3 Medium2025-04-01
CVE-2025-31774 WordPress plugin Astra Security Suite plugin<= 0.2 - Broken Access Control vulnerability — Astra Security Suite 5.3 Medium2025-04-01
CVE-2025-31773 WordPress Ship Per Product plugin <= 2.1.0 - Broken Access Control vulnerability — Ship Per Product 5.3 Medium2025-04-01
CVE-2025-31765 WordPress GDPR Cookie Notice plugin <= 1.2.0 - Broken Access Control vulnerability — GDPR Cookie Notice 5.3 Medium2025-04-01
CVE-2025-31757 WordPress Free Woocommerce Product Table View plugin <= 1.78 - Broken Access Control vulnerability — Free Woocommerce Product Table View 5.4 Medium2025-04-01
CVE-2025-31755 WordPress pCloud Backup plugin <= 1.0.1 - Broken Access Control vulnerability — pCloud Backup 4.3 Medium2025-04-01
CVE-2025-31752 WordPress Bulk Fields Editor plugin <= 1.8.0 - Broken Access Control vulnerability — Bulk Fields Editor 4.3 Medium2025-04-01
CVE-2025-31732 WordPress GB Gallery Slideshow plugin <= 1.3 - Broken Access Control vulnerability — GB Gallery Slideshow 4.3 Medium2025-04-01
CVE-2025-31408 WordPress Zoho Flow plugin <= 2.13.3 - Broken Access Control vulnerability — Zoho Flow 4.3 Medium2025-04-01
CVE-2025-31415 WordPress YayExtra <= 1.5.2 - Broken Access Control Vulnerability — YayExtra 7.6 High2025-04-01
CVE-2025-30926 WordPress King Addons for Elementor plugin <= 24.12.58 - Broken Access Control Vulnerability — King Addons for Elementor 4.3 Medium2025-04-01
CVE-2025-30880 WordPress JS Help Desk plugin <= 2.9.2 - Broken Access Control vulnerability — JS Help Desk 7.5 High2025-04-01
CVE-2025-30797 WordPress Greek Multi Tool – Fix peralinks, accents, auto create menus and more plugin <= 2.3.1 - Broken Access Control Vulnerability — Greek Multi Tool – Fix peralinks, accents, auto create menus and more 7.5 High2025-04-01
CVE-2025-31691 OAuth2 Server - Moderately critical - Access bypass - SA-CONTRIB-2025-020 — OAuth2 Server 7.5 -2025-03-31
CVE-2025-31686 Open Social - Less critical - Access bypass, Information Disclosure - SA-CONTRIB-2025-015 — Open Social 7.5 -2025-03-31
CVE-2025-31685 Open Social - Moderately critical - Access bypass - SA-CONTRIB-2025-014 — Open Social 7.5 -2025-03-31
CVE-2025-31681 Authenticator Login - Critical - Access bypass - SA-CONTRIB-2025-009 — Authenticator Login 7.5 -2025-03-31
CVE-2025-31678 AI (Artificial Intelligence) - Moderately critical - Access bypass, Information Disclosure - SA-CONTRIB-2025-004 — AI (Artificial Intelligence) 9.4 -2025-03-31
CVE-2025-31618 WordPress Connector to CiviCRM with CiviMcRestFace plugin <= 1.0.10 - Broken Access Control vulnerability — Connector to CiviCRM with CiviMcRestFace 5.3 Medium2025-03-31
CVE-2025-31611 WordPress Auto Post After Image Upload plugin <= 1.6 - Broken Access Control vulnerability — Auto Post After Image Upload 4.3 Medium2025-03-31
CVE-2025-31609 WordPress WPCargo Track & Trace plugin <= 8.0.2 - Insecure Direct Object References (IDOR) vulnerability — WPCargo Track & Trace 4.3 Medium2025-03-31
CVE-2025-31606 WordPress SP Blog Designer plugin <= 1.0.0 - Arbitrary Shortcode Execution vulnerability — SP Blog Designer 4.8 Medium2025-03-31

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