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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

5967 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)
ConfidentialityRead 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.
IntegrityModify 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 ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
AvailabilityDoS: 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 DesignDivide 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 DesignEnsure 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 DesignUse 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 DesignFor 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, InstallationUse 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 IDTitleCVSSSeverityPublished
CVE-2025-29010 WordPress Behance Portfolio Manager plugin <= 1.7.5 - Broken Access Control vulnerability — Behance Portfolio Manager 4.3 Medium2025-06-06
CVE-2025-30624 WordPress WordLift plugin <= 3.54.4 - Broken Access Control Vulnerability — WordLift 4.3 Medium2025-06-06
CVE-2025-29013 WordPress Custom Category/Post Type Post order plugin <= 1.6.0 - Broken Access Control Vulnerability — Custom Category/Post Type Post order 5.4 Medium2025-06-06
CVE-2025-30636 WordPress Accessibility Suite plugin <= 4.19 - Broken Access Control Vulnerability — Accessibility Suite 5.4 Medium2025-06-06
CVE-2025-30927 WordPress Wordapp plugin <= 1.7.0 - Broken Access Control Vulnerability — Wordapp 4.3 Medium2025-06-06
CVE-2025-30932 WordPress WP Compress for MainWP plugin <= 6.30.32 - Broken Access Control Vulnerability — WP Compress for MainWP 5.4 Medium2025-06-06
CVE-2025-30934 WordPress 診断ジェネレータ作成プラグイン plugin <= 1.4.16 - Broken Access Control Vulnerability — 診断ジェネレータ作成プラグイン 5.3 Medium2025-06-06
CVE-2025-30945 WordPress Taskbuilder plugin <= 4.0.7 - Broken Access Control Vulnerability — Taskbuilder 5.3 Medium2025-06-06
CVE-2025-30957 WordPress Activity Plus Reloaded for BuddyPress plugin <= 1.1.2 - Broken Access Control Vulnerability — Activity Plus Reloaded for BuddyPress 5.4 Medium2025-06-06
CVE-2025-30958 WordPress onOffice for WP-Websites plugin <= 6.5.1 - Broken Access Control vulnerability — onOffice for WP-Websites 5.4 Medium2025-06-06
CVE-2025-30974 WordPress Post Grid Master plugin <= 3.4.17 - Broken Access Control vulnerability — Post Grid Master 4.3 Medium2025-06-06
CVE-2025-30978 WordPress Slack Notifications by dorzki plugin <= 2.0.7 - Broken Access Control Vulnerability — Slack Notifications by dorzki 4.3 Medium2025-06-06
CVE-2025-30990 WordPress ThemeHunk plugin <= 1.2.0 - Broken Access Control vulnerability — ThemeHunk 4.3 Medium2025-06-06
CVE-2025-31000 WordPress Payment QR WooCommerce plugin <= 1.1.6 - Broken Access Control Vulnerability — Payment QR WooCommerce 5.3 Medium2025-06-06
CVE-2025-49324 WordPress Job Board Manager plugin <= 2.1.60 - Broken Access Control Vulnerability — Job Board Manager 5.3 Medium2025-06-06
CVE-2025-49320 WordPress FraudLabs Pro for WooCommerce plugin <= 2.22.11 - Broken Access Control Vulnerability — FraudLabs Pro for WooCommerce 5.3 Medium2025-06-06
CVE-2025-49293 WordPress Crawlomatic Multisite Scraper Post Generator plugin <= 2.6.8.2 - Broken Access Control Vulnerability — Crawlomatic Multisite Scraper Post Generator 4.3 Medium2025-06-06
CVE-2025-49289 WordPress PDF for WPForms plugin <= 5.5.0 - Broken Access Control Vulnerability — PDF for WPForms 5.0 Medium2025-06-06
CVE-2025-49288 WordPress Ultimate WP Mail plugin <= 1.3.5 - Account Takeover via Email Log Leak Vulnerability — Ultimate WP Mail 8.8 High2025-06-06
CVE-2025-49287 WordPress Product Feed for WooCommerce plugin <= 2.2.8 - Broken Access Control Vulnerability — Product Feed for WooCommerce 4.3 Medium2025-06-06
CVE-2025-49270 WordPress WP-CRM System plugin <= 3.4.2 - Broken Access Control Vulnerability — WP-CRM System 5.3 Medium2025-06-06
CVE-2025-49272 WordPress Trinity Audio plugin <= 5.20.0 - Broken Access Control Vulnerability — Trinity Audio 4.3 Medium2025-06-06
CVE-2025-49268 WordPress Verge3D plugin <= 4.9.4 - Broken Access Control Vulnerability — Verge3D 5.3 Medium2025-06-06
CVE-2025-49246 WordPress Testimonials Showcase plugin <= 1.9.16 - Broken Access Control Vulnerability — Testimonials Showcase 4.3 Medium2025-06-06
CVE-2025-49248 WordPress Team Showcase plugin < 25.05.13 - Broken Access Control Vulnerability — Team Showcase 4.3 Medium2025-06-06
CVE-2025-49241 WordPress oik plugin <= 4.15.1 - Broken Access Control Vulnerability — oik 5.3 Medium2025-06-06
CVE-2025-49240 WordPress DocsPress plugin <= 2.5.2 - Broken Access Control Vulnerability — DocsPress 4.3 Medium2025-06-06
CVE-2025-49236 WordPress Raychat plugin <= 2.1.0 - Broken Access Control Vulnerability — Raychat 5.3 Medium2025-06-06
CVE-2025-48335 WordPress Responsive Plus plugin <= 3.2.0 - Broken Access Control vulnerability — Responsive Plus 5.4 Medium2025-06-06
CVE-2025-48337 WordPress QuickCab plugin <= 1.3.3 - Broken Access Control vulnerability — QuickCab 5.3 Medium2025-06-06

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