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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

5581 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-2026-24357 WordPress WP Recipe Maker plugin <= 10.2.4 - Broken Access Control vulnerability — WP Recipe Maker 4.3 Medium2026-01-22
CVE-2026-24353 WordPress User Registration plugin <= 4.4.9 - Arbitrary Shortcode Execution vulnerability — User Registration 4.3 Medium2026-01-22
CVE-2026-22472 WordPress Easy Form Builder plugin <= 3.9.6 - Broken Access Control vulnerability — Easy Form Builder 4.3 Medium2026-01-22
CVE-2026-22481 WordPress BD Courier Order Ratio Checker plugin <= 2.0.1 - Broken Access Control vulnerability — BD Courier Order Ratio Checker 4.3 Medium2026-01-22
CVE-2026-23974 WordPress Golo theme < 1.7.5 - Broken Access Control vulnerability — Golo 5.3 Medium2026-01-22
CVE-2026-22468 WordPress Absolute Addons For Elementor plugin <= 1.0.14 - Broken Access Control vulnerability — Absolute Addons For Elementor 4.3 Medium2026-01-22
CVE-2026-22466 WordPress WP MapIt plugin <= 3.0.3 - Broken Access Control vulnerability — WP MapIt 4.3 Medium2026-01-22
CVE-2026-22461 WordPress CTX Feed plugin <= 6.6.18 - Broken Access Control vulnerability — CTX Feed 5.3 Medium2026-01-22
CVE-2026-22458 WordPress Wanderland theme <= 1.5 - Broken Access Control vulnerability — Wanderland 4.3 Medium2026-01-22
CVE-2026-22447 WordPress Prowess theme <= 1.8.1 - Broken Access Control vulnerability — Prowess 4.3 Medium2026-01-22
CVE-2026-22445 WordPress Apimo Connector plugin <= 2.6.5.2 - Broken Access Control vulnerability — Apimo Connector 5.3 Medium2026-01-22
CVE-2026-22450 WordPress Don Peppe theme <= 1.3 - Broken Access Control vulnerability — Don Peppe 4.3 Medium2026-01-22
CVE-2026-22348 WordPress Civic Cookie Control plugin <= 1.53 - Broken Access Control vulnerability — Civic Cookie Control 5.3 Medium2026-01-22
CVE-2025-69315 WordPress Simply Schedule Appointments plugin <= 1.6.9.15 - Broken Access Control vulnerability — Simply Schedule Appointments 6.5 Medium2026-01-22
CVE-2025-69300 WordPress Premium Addons for Elementor plugin <= 4.11.63 - Settings Change vulnerability — Premium Addons for Elementor 5.4 Medium2026-01-22
CVE-2025-69311 WordPress Broadstreet Ads plugin <= 1.52.1 - Broken Access Control vulnerability — Broadstreet Ads 7.6 High2026-01-22
CVE-2025-69313 WordPress PostX plugin <= 5.0.3 - Broken Access Control vulnerability — PostX 7.5 High2026-01-22
CVE-2025-69192 WordPress Real Estate Pro plugin <= 2.1.5 - Broken Access Control vulnerability — Real Estate Pro 7.3 High2026-01-22
CVE-2025-69193 WordPress WP Membership plugin <= 1.6.4 - Broken Access Control vulnerability — WP Membership 7.3 High2026-01-22
CVE-2025-69187 WordPress Final User plugin <= 1.2.5 - Broken Access Control vulnerability — Final User 7.3 High2026-01-22
CVE-2025-69188 WordPress fitness-trainer plugin <= 1.7.1 - Broken Access Control vulnerability — fitness-trainer 7.3 High2026-01-22
CVE-2025-69190 WordPress Listihub theme <= 1.0.6 - Broken Access Control vulnerability — Listihub 7.3 High2026-01-22
CVE-2025-69191 WordPress ListingHub plugin <= 1.2.7 - Broken Access Control vulnerability — ListingHub 7.3 High2026-01-22
CVE-2025-69184 WordPress Institutions Directory plugin <= 1.3.4 - Broken Access Control vulnerability — Institutions Directory 7.3 High2026-01-22
CVE-2025-69185 WordPress Hotel Listing plugin <= 1.4.2 - Broken Access Control vulnerability — Hotel Listing 7.3 High2026-01-22
CVE-2025-69186 WordPress Hospital Doctor Directory plugin <= 1.3.9 - Broken Access Control vulnerability — Hospital Doctor Directory 7.3 High2026-01-22
CVE-2025-69181 WordPress Lawyer Directory plugin <= 1.3.4 - Broken Access Control vulnerability — Lawyer Directory 7.3 High2026-01-22
CVE-2025-69095 WordPress Reservation Plugin plugin <= 1.7 - Settings Change vulnerability — Reservation Plugin 6.5 Medium2026-01-22
CVE-2025-69052 WordPress Registration & Login with Mobile Phone Number for WooCommerce plugin <= 1.3.1 - Broken Access Control vulnerability — Registration & Login with Mobile Phone Number for WooCommerce 9.8 Critical2026-01-22
CVE-2025-68911 WordPress Solace theme <= 2.1.16 - Broken Access Control vulnerability — Solace 6.5 Medium2026-01-22

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