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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6886 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-2026-65468 WordPress JetBooking plugin <= 4.1.2 - Broken Access Control vulnerability — JetBooking 5.3 Medium 2026-07-23
CVE-2026-65469 WordPress AWP Classifieds plugin <= 4.4.7 - Broken Access Control vulnerability — AWP Classifieds 5.3 Medium 2026-07-23
CVE-2026-65457 WordPress ЮKassa для WooCommerce plugin <= 2.16.1 - Broken Access Control vulnerability — ЮKassa для WooCommerce 4.3 Medium 2026-07-23
CVE-2026-65453 WordPress Ebook Store plugin <= 6.19 - Broken Access Control vulnerability — Ebook Store 5.3 Medium 2026-07-23
CVE-2026-65452 WordPress Ebook Store plugin <= 6.19 - Broken Access Control vulnerability — Ebook Store 5.3 Medium 2026-07-23
CVE-2026-61973 WordPress ShopLentor Pro plugin <= 2.8.5 - Broken Access Control vulnerability — ShopLentor Pro 4.3 Medium 2026-07-23
CVE-2026-61954 WordPress PayU India plugin <= 3.8.9 - Broken Access Control vulnerability — PayU India 7.5 High 2026-07-23
CVE-2026-61972 WordPress ShopLentor Pro plugin <= 2.8.5 - Broken Access Control vulnerability — ShopLentor Pro 5.3 Medium 2026-07-23
CVE-2026-61943 WordPress WPDM – Premium Packages plugin <= 6.2.0 - Broken Access Control vulnerability — WPDM – Premium Packages 7.5 High 2026-07-23
CVE-2026-59547 WordPress Payment Gateway for PayPal on WooCommerce plugin <= 9.1.4 - Broken Access Control vulnerability — Payment Gateway for PayPal on WooCommerce 7.5 High 2026-07-23
CVE-2026-59522 WordPress WP ERP plugin <= 1.17.5 - Broken Access Control vulnerability — WP ERP 6.5 Medium 2026-07-23
CVE-2026-57808 WordPress WP EasyPay plugin <= 4.5.0 - Arbitrary Content Deletion vulnerability — WP EasyPay 6.5 Medium 2026-07-23
CVE-2026-57717 WordPress Knit Pay plugin <= 9.6.0.0 - Broken Access Control vulnerability — Knit Pay 6.5 Medium 2026-07-23
CVE-2026-57703 WordPress Sunshine Photo Cart plugin <= 3.6.10.1 - Broken Access Control vulnerability — Sunshine Photo Cart 6.3 Medium 2026-07-23
CVE-2026-57425 WordPress Autopay dla WooCommerce plugin <= 2.2.27 - Broken Access Control vulnerability — Autopay dla WooCommerce 6.5 Medium 2026-07-23
CVE-2026-57367 WordPress WP Booking System plugin < 5.12.8.1 - Broken Access Control vulnerability — WP Booking System 7.1 High 2026-07-23
CVE-2026-27423 WordPress Participants Database plugin <= 2.7.8.4 - Broken Access Control vulnerability — Participants Database 4.3 Medium 2026-07-23
CVE-2026-27422 WordPress YT Player plugin <= 2.0.9 - Broken Access Control vulnerability — YT Player 5.3 Medium 2026-07-23
CVE-2026-27418 WordPress WP Fast Total Search plugin <= 1.81.282 - Broken Access Control vulnerability — WP Fast Total Search 5.3 Medium 2026-07-23
CVE-2026-27392 WordPress uListing plugin <= 2.2.0 - Broken Access Control vulnerability — uListing 4.3 Medium 2026-07-23
CVE-2026-27399 WordPress MarketKing plugin <= 2.1.40 - Broken Access Control vulnerability — MarketKing 5.3 Medium 2026-07-23
CVE-2026-27391 WordPress uListing plugin <= 2.2.0 - Broken Access Control vulnerability — uListing 5.4 Medium 2026-07-23
CVE-2026-27377 WordPress QuickCal - Appointment Booking Calendar for WordPress plugin <= 1.0.16 - Broken Access Control vulnerability — QuickCal - Appointment Booking Calendar for WordPress 6.7 Medium 2026-07-23
CVE-2026-27355 WordPress Ditty plugin <= 3.1.66 - Broken Access Control vulnerability — Ditty 5.3 Medium 2026-07-23
CVE-2026-25466 WordPress WP Go Maps plugin <= 10.1.04 - Broken Access Control vulnerability — WP Go Maps 5.3 Medium 2026-07-23
CVE-2026-25427 WordPress eRoom plugin <= 1.7.1 - Broken Access Control vulnerability — eRoom 5.4 Medium 2026-07-23
CVE-2026-25424 WordPress Mediavine Control Panel plugin <= 2.10.10 - Broken Access Control vulnerability — Mediavine Control Panel 4.3 Medium 2026-07-23
CVE-2026-15015 MountDev AI MCP Connector for WordPress <= 1.6.1 - Unauthenticated Privilege Escalation via OAuth Authorization Endpoint — MountDev AI MCP Connector for WordPress 9.8 Critical 2026-07-23
CVE-2026-15827 GutenKit <= 2.4.12 - Missing Authorization to Unauthenticated Sensitive Information Exposure via Mailchimp REST Endpoints — GutenKit – Page Builder Blocks, Patterns, and Templates for Gutenberg Block Editor 5.3 Medium 2026-07-23
CVE-2026-59677 Process Kill Attack Vector in killall() in seunshare — selinux 6.8 Medium 2026-07-23

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