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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6052 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-2023-45633 WordPress IMPress Listings plugin <= 2.6.2 - Broken Access Control vulnerability — IMPress Listings 6.5 Medium2025-01-02
CVE-2022-41995 WordPress Photo Gallery – Image Gallery by Ape Plugin <= 2.2.8 is vulnerable to Broken Access Control — Gallery Images Ape 4.3 Medium2025-01-02
CVE-2022-43476 WordPress Subscribe to Category Plugin <= 2.7.4 is vulnerable to Broken Access Control — Subscribe to Category 4.3 Medium2025-01-02
CVE-2023-47778 WordPress LuckyWP Scripts Control plugin <= 1.2.1 - Broken Access Control vulnerability — LuckyWP Scripts Control 4.3 Medium2025-01-02
CVE-2023-47807 WordPress 10WebAnalytics plugin <= 1.2.12 - Broken Access Control vulnerability — 10WebAnalytics 4.3 Medium2025-01-02
CVE-2023-48739 WordPress Porto Theme Functionality plugin < 2.12.1 - Broken Access Control vulnerability — Porto Theme - Functionality 5.3 Medium2025-01-02
CVE-2023-48758 WordPress JetEngine plugin <= 3.2.4 - Broken Access Control vulnerability — JetEngine 7.1 High2025-01-02
CVE-2024-56266 WordPress MP3 Audio Player plugin <= 5.8 - Broken Access Control vulnerability — MP3 Audio Player for Music, Radio & Podcast by Sonaar 6.3 Medium2025-01-02
CVE-2024-56255 WordPress AyeCode Connect plugin <= 1.3.8 - Broken Access Control vulnerability — AyeCode Connect 4.3 Medium2025-01-02
CVE-2024-56253 WordPress Data Tables Generator by Supsystic plugin <= 1.10.36 - Broken Access Control vulnerability — Data Tables Generator by Supsystic 5.4 Medium2025-01-02
CVE-2024-56244 WordPress Ashe Extra plugin <= 1.2.92 - Broken Access Control vulnerability — Ashe Extra 5.4 Medium2025-01-02
CVE-2024-56243 WordPress WPSSO Core plugin <= 18.18.1 - Broken Access Control vulnerability — WPSSO Core 4.3 Medium2025-01-02
CVE-2024-56238 WordPress Floating Action Buttons plugin <= 0.9.1 - Broken Access Control vulnerability — Floating Action Buttons 5.3 Medium2025-01-02
CVE-2024-56236 WordPress Hestia Nginx Cache plugin <= 2.4.0 - Cross Site Request Forgery (CSRF) vulnerability — Hestia Nginx Cache 4.3 Medium2025-01-02
CVE-2023-47693 WordPress Ultimate Addons for Contact Form 7 plugin <= 3.2.6 - Broken Access Control vulnerability — Ultimate Addons for Contact Form 7 7.5 High2025-01-02
CVE-2023-47692 WordPress Flo Forms plugin <= 1.0.41 - Broken Access Control vulnerability — Flo Forms 4.3 Medium2025-01-02
CVE-2023-47689 WordPress Animator plugin <= 3.0.10 - Unauthenticated Plugin Settings Change Vulnerability — Animator 6.5 Medium2025-01-02
CVE-2023-47661 WordPress Dragfy Addons for Elementor plugin <= 1.0.2 - Broken Access Control + CSRF vulnerability — Dragfy Addons for Elementor 5.4 Medium2025-01-02
CVE-2023-47648 WordPress EazyDocs plugin <= 2.3.5 - Broken Access Control vulnerability — EazyDocs 7.5 High2025-01-02
CVE-2023-47647 WordPress BadgeOS plugin <= 3.7.1.6 - Broken Access Control vulnerability — BadgeOS 4.3 Medium2025-01-02
CVE-2023-47557 WordPress Visitor Traffic Real Time Statistics plugin <= 7.2 - Broken Access Control vulnerability — Visitors Traffic Real Time Statistics 4.3 Medium2025-01-02
CVE-2023-47523 WordPress Auto Tag Creator plugin <= 1.0.2 - Broken Access Control vulnerability — Auto Tag Creator 4.3 Medium2025-01-02
CVE-2023-47515 WordPress Seers | GDPR & CCPA Cookie Consent & Compliance plugin <= 8.1.1 - Broken Access Control vulnerability — Seers 5.3 Medium2025-01-02
CVE-2023-47225 WordPress Short URL plugin <= 1.6.8 - Broken Access Control vulnerability — Short URL 5.4 Medium2025-01-02
CVE-2023-47241 WordPress CoCart – Headless ecommerce plugin <= 3.11.2 - Broken Access Control vulnerability — CoCart – Headless ecommerce 5.3 Medium2025-01-02
CVE-2023-47188 WordPress Simple Job Board plugin <= 2.10.5 - Broken Access Control vulnerability — Simple Job Board 5.3 Medium2025-01-02
CVE-2023-47224 WordPress WP Travel plugin <= 7.8.0 - Broken Access Control vulnerability — WP Travel 7.5 High2025-01-02
CVE-2023-47187 WordPress Animated Rotating Words plugin <= 5.4 - Broken Access Control vulnerability — Animated Rotating Words 5.4 Medium2025-01-02
CVE-2023-47180 WordPress Finale Lite – Sales Countdown Timer & Discount for WooCommerce plugin <= 2.16.0 - Arbitrary Content Deletion vulnerability — Finale Lite 6.5 Medium2025-01-02
CVE-2023-47183 WordPress GiveWP plugin <= 2.33.1 - Broken Access Control vulnerability — GiveWP 5.3 Medium2025-01-02

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