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-2021-47701 OpenBMCS User Management Privilege Escalation — OpenBMCS 8.8AI High AI 2025-12-09
CVE-2022-46845 WordPress Slider a SlidersPack plugin <= 2.0.2 - Broken Access Control vulnerability — Slider a SlidersPack 5.3 Medium 2025-12-09
CVE-2022-47425 WordPress ARMember – Membership Plugin, Content Restriction, Member Levels, User Profile & User signup plugin <= 3.4.10 - Broken Access Control — ARMember 4.3 Medium 2025-12-09
CVE-2023-23729 WordPress Spectra – WordPress Gutenberg Blocks plugin <= 2.3.0 - Contributor+ reCAPTCHA Settings Change Vulnerability — Spectra 5.4 Medium 2025-12-09
CVE-2025-63077 WordPress Happy Addons for Elementor plugin <= 3.20.3 - Broken Access Control vulnerability — Happy Addons for Elementor 4.3 Medium 2025-12-09
CVE-2025-63067 WordPress Porto Theme - Functionality plugin < 3.7.3 - Broken Access Control vulnerability — Porto Theme - Functionality 4.3 Medium 2025-12-09
CVE-2025-63069 WordPress Ivory Search plugin <= 5.5.12 - Broken Access Control vulnerability — Ivory Search 5.3 Medium 2025-12-09
CVE-2025-63063 WordPress Yandex.Metrica plugin <= 1.2.2 - Broken Access Control vulnerability — Yandex.Metrica 5.3 Medium 2025-12-09
CVE-2025-63056 WordPress Contact Form by BestWebSoft plugin <= 4.3.6 - Broken Access Control vulnerability — Contact Form by BestWebSoft 4.3 Medium 2025-12-09
CVE-2025-63054 WordPress Quiz And Survey Master plugin <= 10.3.2 - Broken Access Control vulnerability — Quiz And Survey Master 5.3 Medium 2025-12-09
CVE-2025-63049 WordPress ListingPro Lead Form plugin <= 1.0.7 - Broken Access Control vulnerability — ListingPro Lead Form 5.3 Medium 2025-12-09
CVE-2025-63047 WordPress ListingPro theme <= 2.9.9 - Broken Access Control vulnerability — ListingPro 5.3 Medium 2025-12-09
CVE-2025-63034 WordPress Page View Count plugin <= 2.9.0 - Settings Change vulnerability — Page View Count 5.4 Medium 2025-12-09
CVE-2025-63024 WordPress Order Delivery Date for WooCommerce plugin <= 4.3.1 - Broken Access Control vulnerability — Order Delivery Date for WooCommerce 5.4 Medium 2025-12-09
CVE-2025-63028 WordPress Traveler theme <= 3.2.6 - Broken Access Control vulnerability — Traveler 5.3 Medium 2025-12-09
CVE-2025-63025 WordPress Xagio SEO plugin <= 7.1.0.37 - Broken Access Control vulnerability — Xagio SEO 4.3 Medium 2025-12-09
CVE-2025-63015 WordPress WooCommerce Payment Gateway – Paysera plugin <= 3.10.0 - Broken Access Control vulnerability — WooCommerce Payment Gateway - Paysera 4.3 Medium 2025-12-09
CVE-2025-63023 WordPress Payment Gateway for PayPal on WooCommerce plugin <= 9.0.53 - Broken Access Control vulnerability — Payment Gateway for PayPal on WooCommerce 5.3 Medium 2025-12-09
CVE-2025-63008 WordPress WP ERP plugin <= 1.16.7 - Broken Access Control vulnerability — WP ERP 5.3 Medium 2025-12-09
CVE-2025-63006 WordPress EventPrime plugin <= 4.2.4.1 - Broken Access Control vulnerability — EventPrime 4.3 Medium 2025-12-09
CVE-2025-62999 WordPress Litho Addons plugin <= 3.5 - Broken Access Control vulnerability — Litho Addons 5.4 Medium 2025-12-09
CVE-2025-62996 WordPress Custom Layouts – Post + Product grids made easy plugin <= 1.4.12 - Broken Access Control vulnerability — Custom Layouts – Post + Product grids made easy 4.3 Medium 2025-12-09
CVE-2025-62995 WordPress MultiParcels Shipping For WooCommerce plugin <= 1.30.12 - Broken Access Control vulnerability — MultiParcels Shipping For WooCommerce 4.3 Medium 2025-12-09
CVE-2025-62993 WordPress Notification for Telegram plugin <= 3.5.1 - Broken Access Control vulnerability — Notification for Telegram 4.3 Medium 2025-12-09
CVE-2025-62870 WordPress Eupago Gateway For Woocommerce plugin <= 4.7.1 - Broken Access Control vulnerability — Eupago Gateway For Woocommerce 5.3 Medium 2025-12-09
CVE-2025-62869 WordPress Gravitec.net – Web Push Notifications plugin <= 2.9.17 - Broken Access Control vulnerability — Gravitec.net – Web Push Notifications 4.3 Medium 2025-12-09
CVE-2025-62867 WordPress Ergonet Cache plugin <= 1.0.13 - Broken Access Control vulnerability — Ergonet Cache 4.3 Medium 2025-12-09
CVE-2025-62865 WordPress Post Cloner plugin <= 1.0.0 - Broken Access Control vulnerability — Post Cloner 5.3 Medium 2025-12-09
CVE-2025-62740 WordPress WP-CRM System plugin <= 3.4.6 - Broken Access Control vulnerability — WP-CRM System 5.3 Medium 2025-12-09
CVE-2025-62738 WordPress Formstack Online Forms plugin <= 2.0.2 - Broken Access Control vulnerability — Formstack Online Forms 5.3 Medium 2025-12-09

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