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-64219 WordPress Business Directory plugin <= 6.4.18 - Broken Access Control vulnerability — Business Directory 4.3 Medium 2025-10-29
CVE-2025-64212 WordPress MasterStudy LMS Pro plugin < 4.7.16 - Broken Access Control vulnerability — MasterStudy LMS Pro 5.4 Medium 2025-10-29
CVE-2025-64210 WordPress Masterstudy Elementor Widgets plugin <= 1.2.4 - Broken Access Control vulnerability — Masterstudy Elementor Widgets 5.4 Medium 2025-10-29
CVE-2025-64211 WordPress Masterstudy Elementor Widgets plugin <= 1.2.4 - Broken Access Control vulnerability — Masterstudy Elementor Widgets 5.3 Medium 2025-10-29
CVE-2025-64199 WordPress wpresidence theme <= 5.3.2 - Broken Access Control vulnerability — wpresidence 5.3 Medium 2025-10-29
CVE-2025-58711 WordPress Blog Designer PRO plugin <= 3.4.8 - Broken Access Control vulnerability — Blog Designer PRO 5.3 Medium 2025-10-29
CVE-2025-11702 Missing Authorization in GitLab — GitLab 8.5 High 2025-10-29
CVE-2025-11705 Anti-Malware Security and Brute-Force Firewall <= 4.23.81 - Missing Authorization to Authenticated (Subscriber+) Arbitrary File Read — Anti-Malware Security and Brute-Force Firewall 6.5 Medium 2025-10-29
CVE-2025-64296 WordPress Facebook for WooCommerce plugin <= 3.5.7 - Broken Access Control to Notice Dismissal vulnerability — Facebook for WooCommerce 5.3 Medium 2025-10-29
CVE-2025-59461 API does not require authentication — TLOC100-100 all Firmware versions 7.6 High 2025-10-27
CVE-2025-62980 WordPress Persian Admnin Fonts plugin <= 4.1.03 - Broken Access Control vulnerability — Persian Admnin Fonts 5.4 Medium 2025-10-27
CVE-2025-62978 WordPress KiotViet Sync plugin <= 1.8.5 - Broken Access Control vulnerability — KiotViet Sync 4.3 Medium 2025-10-27
CVE-2025-62976 WordPress Sendle Shipping plugin <= 6.02 - Broken Access Control vulnerability — Sendle Shipping 5.3 Medium 2025-10-27
CVE-2025-62977 WordPress 百度站长SEO合集(支持百度/神马/Bing/头条推送) plugin <= 2.1.4 - Broken Access Control vulnerability — 百度站长SEO合集(支持百度/神马/Bing/头条推送) 5.3 Medium 2025-10-27
CVE-2025-62973 WordPress BuddyForms plugin <= 2.9.0 - Broken Access Control vulnerability — BuddyForms 5.3 Medium 2025-10-27
CVE-2025-62972 WordPress WebinarPress plugin <= 1.33.28 - Broken Access Control vulnerability — WebinarPress 4.3 Medium 2025-10-27
CVE-2025-62970 WordPress Link Whisper Free plugin <= 0.9.2 - Broken Access Control vulnerability — Link Whisper Free 5.3 Medium 2025-10-27
CVE-2025-62966 WordPress GoCache plugin <= 1.3.6 - Broken Access Control vulnerability — GoCache 5.4 Medium 2025-10-27
CVE-2025-62965 WordPress Admin Management Xtended plugin <= 2.5.1 - Broken Access Control vulnerability — Admin Management Xtended 4.3 Medium 2025-10-27
CVE-2025-62964 WordPress MDTF plugin <= 1.3.6 - Broken Access Control vulnerability — MDTF 5.3 Medium 2025-10-27
CVE-2025-62953 WordPress Welcart e-Commerce plugin <= 2.11.24 - Broken Access Control vulnerability — Welcart e-Commerce 4.3 Medium 2025-10-27
CVE-2025-62954 WordPress Revive Old Posts plugin <= 9.3.3 - Broken Access Control vulnerability — Revive Old Posts 4.3 Medium 2025-10-27
CVE-2025-62952 WordPress ChatBot plugin <= 7.7.3 - Broken Access Control vulnerability — ChatBot 4.3 Medium 2025-10-27
CVE-2025-62946 WordPress Everest Backup plugin <= 2.3.8 - Broken Access Control vulnerability — Everest Backup 5.3 Medium 2025-10-27
CVE-2025-62944 WordPress MSTW CSV EXPORTER plugin <= 1.4 - Broken Access Control vulnerability — MSTW CSV EXPORTER 5.3 Medium 2025-10-27
CVE-2025-62938 WordPress Reoon Email Verifier plugin <= 2.0.1 - Broken Access Control vulnerability — Reoon Email Verifier 4.3 Medium 2025-10-27
CVE-2025-62935 WordPress Open Close WooCommerce Store plugin <= 5.0.0 - Broken Access Control vulnerability — Open Close WooCommerce Store 4.3 Medium 2025-10-27
CVE-2025-62932 WordPress Table Block by RioVizual plugin <= 3.0.0 - Broken Access Control vulnerability — Table Block by RioVizual 4.3 Medium 2025-10-27
CVE-2025-62929 WordPress Testimonial Slider plugin <= 2.0.15 - Broken Access Control vulnerability — Testimonial Slider 6.5 Medium 2025-10-27
CVE-2025-62931 WordPress MSN Partner Hub plugin <= 2.9 - Broken Access Control vulnerability — MSN Partner Hub 4.3 Medium 2025-10-27

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