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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6923 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)
Confidentiality Read 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.
Integrity Modify 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 Control Gain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Availability DoS: 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 Design Divide 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 Design Ensure 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 Design Use 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 Design For 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, Installation Use 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 ID Title CVSS Severity Published
CVE-2025-39350 WordPress wProject theme < 5.8.0 - Unauthenticated Post/Comment/Attachment Modification/Deletion vulnerability — wProject 8.2 High 2025-05-19
CVE-2025-39352 WordPress Grand Restaurant WordPress theme <= 7.0 - Arbitrary Options Deletion vulnerability — Grand Restaurant 8.2 High 2025-05-19
CVE-2025-39447 WordPress JetElements For Elementor plugin <= 2.7.4.1 - Broken Access Control Vulnerability — JetElements For Elementor 7.5 High 2025-05-19
CVE-2025-39449 WordPress JetWooBuilder plugin <= 2.1.18 - Broken Access Control Vulnerability — JetWooBuilder 7.5 High 2025-05-19
CVE-2025-39451 WordPress JetBlocks For Elementor plugin <= 1.3.16 - Broken Access Control Vulnerability — JetBlocks For Elementor 7.5 High 2025-05-19
CVE-2025-43838 WordPress Custom PC Builder Lite for WooCommerce <= 1.0.1 - Settings Change Vulnerability — Custom PC Builder Lite for WooCommerce 6.5 Medium 2025-05-19
CVE-2025-22287 WordPress LTL Freight Quotes – FreightQuote Edition plugin <= 2.3.11 - Broken Access Control vulnerability — LTL Freight Quotes – FreightQuote Edition 5.4 Medium 2025-05-19
CVE-2025-39454 WordPress Name Directory plugin <= 1.30.0 - Broken Access Control vulnerability — Name Directory 4.3 Medium 2025-05-19
CVE-2025-39460 WordPress Eduma theme <= 5.6.4 - Broken Access Control vulnerability — Eduma 5.3 Medium 2025-05-19
CVE-2025-39412 WordPress Master Slider plugin <= 3.11.0 - Broken Access Control vulnerability — Master Slider 4.3 Medium 2025-05-19
CVE-2025-39398 WordPress Hotel + Bed and Breakfast Booking Calendar Theme | Bellevue theme <= 4.2.2 - Broken Access Control vulnerability — Bellevue 4.3 Medium 2025-05-19
CVE-2025-26920 WordPress Customify theme <= 0.4.8 - Broken Access Control vulnerability — Customify 5.4 Medium 2025-05-19
CVE-2025-26867 WordPress Bulk theme <= 1.0.11 - Broken Access Control vulnerability — Bulk 5.3 Medium 2025-05-19
CVE-2025-39388 WordPress AnalyticsWP plugin <= 2.0.0 - Broken Access Control vulnerability — AnalyticsWP 5.3 Medium 2025-05-19
CVE-2025-39376 WordPress Car Park Booking System for WordPress plugin <= 2.6 - Broken Access Control vulnerability — Car Park Booking System for WordPress 4.3 Medium 2025-05-19
CVE-2025-39373 WordPress JNews Theme <= 11.6.16 - Broken Access Control Vulnerability — JNews 5.3 Medium 2025-05-19
CVE-2025-39368 WordPress Rootspersona plugin <= 3.7.5 - Broken Access Control vulnerability — Rootspersona 5.3 Medium 2025-05-19
CVE-2025-39353 WordPress Grand Restaurant WordPress theme <= 7.0 - Broken Access Control vulnerability — Grand Restaurant 5.3 Medium 2025-05-19
CVE-2025-48346 WordPress Embed and Integrate Etsy Shop plugin <= 1.0.8 - Broken Access Control vulnerability — Embed and Integrate Etsy Shop 5.3 Medium 2025-05-19
CVE-2025-48282 WordPress Majestic Support plugin <= 1.1.0 - Broken Access Control Vulnerability — Majestic Support 5.3 Medium 2025-05-19
CVE-2025-48272 WordPress WP Job Portal plugin <= 2.3.2 - Insecure Direct Object References (IDOR) Vulnerability — WP Job Portal 5.3 Medium 2025-05-19
CVE-2025-48268 WordPress Bot for Telegram on WooCommerce plugin <= 1.2.6 - Broken Access Control Vulnerability — Bot for Telegram on WooCommerce 4.3 Medium 2025-05-19
CVE-2025-48262 WordPress Url Rewrite Analyzer plugin <= 1.3.3 - Broken Access Control Vulnerability — Url Rewrite Analyzer 4.3 Medium 2025-05-19
CVE-2025-48260 WordPress GDPR CCPA Compliance Support plugin <= 2.7.3 - Broken Access Control Vulnerability — GDPR CCPA Compliance Support 4.3 Medium 2025-05-19
CVE-2025-48257 WordPress Projectopia plugin <= 5.1.17 - Broken Access Control Vulnerability — Projectopia 6.5 Medium 2025-05-19
CVE-2025-48247 WordPress Shortlinks by Pretty Links plugin <= 3.6.15 - Broken Access Control Vulnerability — Shortlinks by Pretty Links 4.3 Medium 2025-05-19
CVE-2025-48246 WordPress The Events Calendar plugin <= 6.11.2.1 - Broken Access Control Vulnerability — The Events Calendar 5.4 Medium 2025-05-19
CVE-2025-48242 WordPress Legal Pages plugin <= 1.4.5 - Broken Access Control Vulnerability — Legal Pages 6.5 Medium 2025-05-19
CVE-2025-4477 TeamT5 ThreatSonar Anti-Ransomware - Privilege Escalation — ThreatSonar Anti-Ransomware 7.2 High 2025-05-19
CVE-2025-3527 EventON - WordPress Virtual Event Calendar Plugin <= 4.9.6 - Missing Authorization to Authenticated (Subscriber+) Stored Cross-Site Scripting — EventON (Pro) - WordPress Virtual Event Calendar Plugin 6.4 Medium 2025-05-17

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