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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

5961 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-67965 WordPress Homey Core plugin <= 2.4.3 - Broken Access Control vulnerability — Homey Core 5.3 Medium2025-12-16
CVE-2025-67976 WordPress Watu Quiz plugin <= 3.4.5 - Broken Access Control vulnerability — Watu Quiz 6.5 Medium2025-12-16
CVE-2025-66167 WordPress Lottier plugin <= 1.1.1 - Broken Access Control vulnerability — Lottier 5.4 Medium2025-12-16
CVE-2025-66166 WordPress Lottier for Elementor plugin <= 1.0.9 - Broken Access Control vulnerability — Lottier for Elementor 5.4 Medium2025-12-16
CVE-2025-67929 WordPress TI WooCommerce Wishlist plugin <= 2.10.0 - Broken Access Control vulnerability — TI WooCommerce Wishlist 5.3 Medium2025-12-16
CVE-2025-66165 WordPress Lottier for WPBakery plugin <= 1.1.7 - Broken Access Control vulnerability — Lottier for WPBakery 5.4 Medium2025-12-16
CVE-2025-66162 WordPress Spoter for Elementor plugin <= 1.04 - Broken Access Control vulnerability — Spoter for Elementor 5.4 Medium2025-12-16
CVE-2025-66163 WordPress Masker for Elementor plugin <= 1.1.4 - Broken Access Control vulnerability — Masker for Elementor 5.4 Medium2025-12-16
CVE-2025-66164 WordPress Laser plugin <= 1.1.1 - Broken Access Control vulnerability — Laser 5.4 Medium2025-12-16
CVE-2025-66147 WordPress Coder for Elementor plugin <= 1.0.13 - Broken Access Control vulnerability — Coder for Elementor 5.4 Medium2025-12-16
CVE-2025-66161 WordPress Grider for Elementor plugin <= 1.0.8 - Broken Access Control vulnerability — Grider for Elementor 5.4 Medium2025-12-16
CVE-2025-66134 WordPress FileBird Pro plugin <= 6.5.1 - Broken Access Control vulnerability — FileBird Pro 5.4 Medium2025-12-16
CVE-2025-66133 WordPress WP Cookie Notice for GDPR, CCPA & ePrivacy Consent plugin <= 4.0.7 - Broken Access Control vulnerability — WP Cookie Notice for GDPR, CCPA & ePrivacy Consent 5.3 Medium2025-12-16
CVE-2025-66131 WordPress Yaad Sarig Payment Gateway For WC plugin <= 2.2.11 - Broken Access Control vulnerability — Yaad Sarig Payment Gateway For WC 5.3 Medium2025-12-16
CVE-2025-66127 WordPress Essential Real Estate plugin <= 5.3.2 - Broken Access Control vulnerability — Essential Real Estate 5.3 Medium2025-12-16
CVE-2025-66129 WordPress Pochipp plugin <= 1.18.0 - Broken Access Control vulnerability — Pochipp 5.3 Medium2025-12-16
CVE-2025-66128 WordPress Sendinblue for WooCommerce plugin <= 4.0.49 - Broken Access Control vulnerability — Sendinblue for WooCommerce 5.3 Medium2025-12-16
CVE-2025-66130 WordPress WP Views Counter plugin <= 2.1.2 - Broken Access Control vulnerability — WP Views Counter 5.3 Medium2025-12-16
CVE-2025-66121 WordPress SiteGround Security plugin <= 1.5.8 - Broken Access Control vulnerability — SiteGround Security 5.3 Medium2025-12-16
CVE-2025-66124 WordPress Leaky Paywall plugin <= 4.22.6 - Broken Access Control vulnerability — Leaky Paywall 5.3 Medium2025-12-16
CVE-2025-66122 WordPress Stylish Price List plugin <= 7.2.2 - Broken Access Control vulnerability — Stylish Price List 5.3 Medium2025-12-16
CVE-2025-66120 WordPress CatFolders plugin <= 2.5.3 - Broken Access Control vulnerability — CatFolders 5.3 Medium2025-12-16
CVE-2025-64635 WordPress Feeds for YouTube plugin <= 2.4.0 - Broken Access Control vulnerability — Feeds for YouTube 5.3 Medium2025-12-16
CVE-2025-64639 WordPress WP Compress for MainWP plugin <= 6.50.17 - Broken Access Control vulnerability — WP Compress for MainWP 5.3 Medium2025-12-16
CVE-2025-64638 WordPress OnPay.io for WooCommerce plugin <= 1.0.47 - Broken Access Control vulnerability — OnPay.io for WooCommerce 5.3 Medium2025-12-16
CVE-2025-64632 WordPress Google XML Sitemaps plugin <= 4.1.22 - Broken Access Control vulnerability — Google XML Sitemaps 5.3 Medium2025-12-16
CVE-2025-64634 WordPress Avada theme <= 7.13.2 - Broken Access Control vulnerability — Avada 5.3 Medium2025-12-16
CVE-2025-64631 WordPress WCFM Marketplace plugin <= 3.7.1 - Broken Access Control vulnerability — WCFM Marketplace 4.9 Medium2025-12-16
CVE-2025-64251 WordPress Ultimate Learning Pro plugin <= 3.9.3 - Arbitrary Content Deletion vulnerability — Ultimate Learning Pro 4.9 Medium2025-12-16
CVE-2025-64630 WordPress Business Directory plugin <= 6.4.19 - Broken Access Control vulnerability — Business Directory 4.9 Medium2025-12-16

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