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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6904 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-69181 WordPress Lawyer Directory plugin <= 1.3.4 - Broken Access Control vulnerability — Lawyer Directory 7.3 High 2026-01-22
CVE-2025-69095 WordPress Reservation Plugin plugin <= 1.7 - Settings Change vulnerability — Reservation Plugin 6.5 Medium 2026-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 Critical 2026-01-22
CVE-2025-68911 WordPress Solace theme <= 2.1.16 - Broken Access Control vulnerability — Solace 6.5 Medium 2026-01-22
CVE-2025-68896 WordPress WDV One Page Docs plugin <= 1.2.4 - Broken Access Control vulnerability — WDV One Page Docs 6.5 Medium 2026-01-22
CVE-2025-68882 WordPress Scalenut plugin <= 1.1.5 - Broken Access Control vulnerability — Scalenut 7.5 High 2026-01-22
CVE-2025-68558 WordPress Depicter Slider plugin <= 4.0.4 - Broken Access Control vulnerability — Depicter Slider 6.5 Medium 2026-01-22
CVE-2025-68073 WordPress GDPR CCPA Compliance Support plugin <= 2.7.4 - Broken Access Control vulnerability — GDPR CCPA Compliance Support 6.5 Medium 2026-01-22
CVE-2025-68507 WordPress Icegram plugin <= 3.1.35 - Broken Access Control vulnerability — Icegram 6.5 Medium 2026-01-22
CVE-2025-68059 WordPress Hotel Listing plugin <= 1.4.2 - Broken Access Control vulnerability — Hotel Listing 7.6 High 2026-01-22
CVE-2025-68072 WordPress Easy Property Listings plugin <= 3.5.20 - Broken Access Control vulnerability — Easy Property Listings 6.5 Medium 2026-01-22
CVE-2025-68058 WordPress Institutions Directory plugin <= 1.3..4 - Broken Access Control vulnerability — Institutions Directory 7.6 High 2026-01-22
CVE-2025-68057 WordPress Hospital Doctor Directory plugin <= 1.3.9 - Broken Access Control vulnerability — Hospital Doctor Directory 7.6 High 2026-01-22
CVE-2025-68039 WordPress WP BackItUp plugin <= 2.1.0 - Broken Access Control vulnerability — WP BackItUp 6.5 Medium 2026-01-22
CVE-2025-68019 WordPress SEO Booster plugin <= 6.1.8 - Broken Access Control vulnerability — SEO Booster 6.5 Medium 2026-01-22
CVE-2025-68020 WordPress Notifier plugin <= 2.7.13 - Broken Access Control vulnerability — Notifier 6.5 Medium 2026-01-22
CVE-2025-68018 WordPress Order Listener for WooCommerce plugin <= 3.6.1 - Broken Access Control vulnerability — Order Listener for WooCommerce 9.4 Critical 2026-01-22
CVE-2025-68016 WordPress onepay Payment Gateway For WooCommerce plugin <= 1.1.2 - Other Vulnerability Type vulnerability — onepay Payment Gateway For WooCommerce 6.5 Medium 2026-01-22
CVE-2025-68013 WordPress Payment Gateway Authorize.Net CIM for WooCommerce plugin <= 2.1.2 - Arbitrary Content Deletion vulnerability — Payment Gateway Authorize.Net CIM for WooCommerce 6.5 Medium 2026-01-22
CVE-2025-68007 WordPress Event Espresso 4 Decaf plugin <= 5.0.37.decaf - Settings Change vulnerability — Event Espresso 4 Decaf 6.5 Medium 2026-01-22
CVE-2025-68009 WordPress Slider Templates plugin <= 1.0.3 - Broken Access Control vulnerability — Slider Templates 6.5 Medium 2026-01-22
CVE-2025-68003 WordPress Shown Connector plugin <= 1.2.10 - Settings Change vulnerability — Shown Connector 6.5 Medium 2026-01-22
CVE-2025-67967 WordPress Lawyer Directory plugin <= 1.3.3 - Broken Access Control vulnerability — Lawyer Directory 7.6 High 2026-01-22
CVE-2025-67958 WordPress TaxCloud for WooCommerce plugin <= 8.3.8 - Broken Access Control vulnerability — TaxCloud for WooCommerce 6.5 Medium 2026-01-22
CVE-2025-67956 WordPress User Registration plugin <= 4.4.6 - Broken Access Control vulnerability — User Registration 8.2 High 2026-01-22
CVE-2025-67942 WordPress Peach Payments Gateway plugin <= 3.3.6 - Broken Access Control vulnerability — Peach Payments Gateway 6.5 Medium 2026-01-22
CVE-2025-67939 WordPress Tickera plugin <= 3.5.6.2 - Broken Access Control vulnerability — Tickera 6.5 Medium 2026-01-22
CVE-2025-66141 WordPress Scroller plugin <= 2.0.2 - Broken Access Control vulnerability — Scroller 5.4 Medium 2026-01-22
CVE-2025-66142 WordPress Comparimager for Elementor plugin <= 1.0.1 - Broken Access Control vulnerability — Comparimager for Elementor 5.4 Medium 2026-01-22
CVE-2025-66143 WordPress Crumber plugin <= 1.0.10 - Broken Access Control vulnerability — Crumber 5.4 Medium 2026-01-22

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