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-59591 WordPress wpDiscuz Plugin <= 7.6.33 - Broken Access Control Vulnerability — wpDiscuz 4.3 Medium 2025-09-22
CVE-2025-53452 WordPress Event Rocket Plugin <= 3.3 - Broken Access Control Vulnerability — Event Rocket 4.3 Medium 2025-09-22
CVE-2025-57899 WordPress WP Compress Plugin <= 6.50.54 - Broken Access Control Vulnerability — WP Compress 5.3 Medium 2025-09-22
CVE-2025-57907 WordPress Heureka Plugin <= 1.1.0 - Broken Access Control Vulnerability — Heureka 5.3 Medium 2025-09-22
CVE-2025-57909 WordPress Editor Custom Color Palette plugin <= 3.5.6 - Broken Access Control vulnerability — Editor Custom Color Palette 6.5 Medium 2025-09-22
CVE-2025-57917 WordPress Printcart Web to Print Product Designer for WooCommerce plugin <= 2.4.8 - Broken Access Control vulnerability — Printcart Web to Print Product Designer for WooCommerce 4.3 Medium 2025-09-22
CVE-2025-57921 WordPress Frontend File Manager plugin <= 23.3 - Broken Access Control vulnerability — Frontend File Manager 5.3 Medium 2025-09-22
CVE-2025-57936 WordPress Subresource Integrity (SRI) Manager Plugin <= 0.4.0 - Broken Access Control Vulnerability — Subresource Integrity (SRI) Manager 4.3 Medium 2025-09-22
CVE-2025-57939 WordPress Image Hover Effects – Elementor Addon Plugin <= 1.4.4 - Broken Access Control Vulnerability — Image Hover Effects – Elementor Addon 5.3 Medium 2025-09-22
CVE-2025-57944 WordPress Skimlinks Affiliate Marketing Tool plugin <= 1.3 - Broken Access Control vulnerability — Skimlinks Affiliate Marketing Tool 5.3 Medium 2025-09-22
CVE-2025-57949 WordPress Ongkoskirim.id Plugin <= 1.0.6 - Broken Access Control Vulnerability — Ongkoskirim.id 5.4 Medium 2025-09-22
CVE-2025-57955 WordPress Post Carousel Slider for Elementor Plugin <= 1.7.0 - Broken Access Control Vulnerability — Post Carousel Slider for Elementor 6.5 Medium 2025-09-22
CVE-2025-57957 WordPress WooMS Plugin <= 9.12 - Broken Access Control Vulnerability — WooMS 5.3 Medium 2025-09-22
CVE-2025-57961 WordPress CoDesigner plugin <= 4.29 - Broken Access Control vulnerability — CoDesigner 4.3 Medium 2025-09-22
CVE-2025-57969 WordPress Hide WP Toolbar Plugin <= 2.7 - Broken Access Control Vulnerability — Hide WP Toolbar 4.3 Medium 2025-09-22
CVE-2025-57971 WordPress SALESmanago Plugin <= 3.8.1 - Broken Access Control Vulnerability — SALESmanago & Leadoo 5.3 Medium 2025-09-22
CVE-2025-57972 WordPress Helpdesk Support Ticket System for WooCommerce plugin <= 2.1.1 - Broken Access Control vulnerability — Helpdesk Support Ticket System for WooCommerce 4.3 Medium 2025-09-22
CVE-2025-57975 WordPress Team Plugin <= 5.0.6 - Broken Access Control Vulnerability — Team 4.3 Medium 2025-09-22
CVE-2025-57976 WordPress CardCom Payment Gateway plugin <= 3.5.0.7 - Broken Access Control vulnerability — CardCom Payment Gateway 5.3 Medium 2025-09-22
CVE-2025-57985 WordPress Ultimate Watermark Plugin <= 1.1 - Broken Access Control Vulnerability — Ultimate Watermark 4.3 Medium 2025-09-22
CVE-2025-57987 WordPress WP Events Manager Plugin <= 2.2.1 - Broken Access Control Vulnerability — WP Events Manager 5.3 Medium 2025-09-22
CVE-2025-57990 WordPress Blog Designer Plugin <= 3.1.8 - Broken Access Control Vulnerability — Blog Designer 5.4 Medium 2025-09-22
CVE-2025-57991 WordPress Clariti Plugin <= 1.2.1 - Broken Access Control Vulnerability — Clariti 5.4 Medium 2025-09-22
CVE-2025-57995 WordPress DethemeKit For Elementor Plugin <= 2.1.10 - Broken Access Control Vulnerability — DethemeKit For Elementor 4.3 Medium 2025-09-22
CVE-2025-57997 WordPress Trustpilot Reviews Plugin <= 2.5.925 - Broken Access Control Vulnerability — Trustpilot Reviews 4.3 Medium 2025-09-22
CVE-2025-58000 WordPress Memberful plugin <= 1.75.0 - Broken Access Control vulnerability — Memberful - Membership Plugin 5.3 Medium 2025-09-22
CVE-2025-58003 WordPress Javo Core Plugin <= 3.0.0.266 - Broken Access Control Vulnerability — Javo Core 5.3 Medium 2025-09-22
CVE-2025-58004 WordPress DriCub Theme <= 2.9 - Broken Access Control Vulnerability — DriCub 5.3 Medium 2025-09-22
CVE-2025-58009 WordPress CP Multi View Event Calendar plugin <= 1.4.35 - Broken Access Control vulnerability — CP Multi View Event Calendar 3.8 Low 2025-09-22
CVE-2025-58016 WordPress CF7 Submissions Plugin <= 0.26 - Broken Access Control Vulnerability — CF7 Submissions 4.3 Medium 2025-09-22

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