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-2023-47183 WordPress GiveWP plugin <= 2.33.1 - Broken Access Control vulnerability — GiveWP 5.3 Medium 2025-01-02
CVE-2023-47179 WordPress WooODT Lite plugin <= 2.4.6 - Arbitrary Site Option Update vulnerability — WooODT Lite 8.8 High 2025-01-02
CVE-2023-46639 WordPress kk Star Ratings plugin <= 5.4.5 - Broken Access Control vulnerability — kk Star Ratings 5.3 Medium 2025-01-02
CVE-2023-46644 WordPress WordPress CTA plugin <= 1.5.8 - Broken Access Control vulnerability — WordPress CTA 6.5 Medium 2025-01-02
CVE-2023-46635 WordPress YITH WooCommerce Product Add-Ons plugin <= 4.2.0 - Broken Access Control vulnerability — YITH WooCommerce Product Add-Ons 5.3 Medium 2025-01-02
CVE-2023-46637 WordPress Generate Dummy Posts plugin <= 1.0.0 - Broken Access Control vulnerability — Generate Dummy Posts 5.3 Medium 2025-01-02
CVE-2023-46633 WordPress WP Glossary plugin <= 3.1.2 - Broken Access Control vulnerability — Glossary 5.4 Medium 2025-01-02
CVE-2023-46632 WordPress My Shortcodes plugin <= 2.3 - Broken Access Control vulnerability — My Shortcodes 7.1 High 2025-01-02
CVE-2023-46631 WordPress Product Recommendation Quiz for eCommerce plugin <= 2.1.2 - Broken Access Control vulnerability — Product Recommendation Quiz for eCommerce 6.5 Medium 2025-01-02
CVE-2023-46628 WordPress WP Word Count plugin <= 3.2.4 - Broken Access Control vulnerability — WP Word Count 4.3 Medium 2025-01-02
CVE-2023-46616 WordPress Draw Attention plugin <= 2.0.15 - Broken Access Control vulnerability — Draw Attention 5.4 Medium 2025-01-02
CVE-2023-46612 WordPress Mediabay plugin <= 1.6 - Broken Access Control vulnerability — Mediabay 4.3 Medium 2025-01-02
CVE-2023-46610 WordPress Quill Forms plugin <= 3.3.0 - Broken Access Control + CSRF vulnerability — Quill Forms 6.5 Medium 2025-01-02
CVE-2023-46609 WordPress FeedFocal plugin <= 1.2.2 - Broken Access Control vulnerability — FeedFocal 6.5 Medium 2025-01-02
CVE-2023-46607 WordPress WP iCal Availability plugin <= 1.0.3 - Broken Access Control vulnerability — WP iCal Availability 5.4 Medium 2025-01-02
CVE-2023-46608 WordPress DoLogin Security plugin <= 3.7.1 - Multiple Broken Access Control vulnerability — DoLogin Security 5.3 Medium 2025-01-02
CVE-2023-46606 WordPress AtomChat plugin <= 1.1.4 - Broken Access Control vulnerability — AtomChat 5.3 Medium 2025-01-02
CVE-2023-46605 WordPress Convertful – Your Ultimate On-Site Conversion Tool plugin <= 2.5 - Broken Access Control vulnerability — Convertful – Your Ultimate On-Site Conversion Tool 5.3 Medium 2025-01-02
CVE-2023-46309 WordPress wpDiscuz plugin <= 7.6.10 - Broken Access Control vulnerability — wpDiscuz 5.3 Medium 2025-01-02
CVE-2023-46206 WordPress MW WP Form plugin <= 4.4.5 - Broken Access Control vulnerability — MW WP Form 5.3 Medium 2025-01-02
CVE-2023-46203 WordPress Just Custom Fields plugin <= 3.3.2 - Broken Access Control vulnerability — Just Custom Fields 4.3 Medium 2025-01-02
CVE-2023-46196 WordPress Social proof testimonials and reviews by Repuso plugin <= 4.97 - Broken Access Control vulnerability — Social proof testimonials and reviews by Repuso 4.3 Medium 2025-01-02
CVE-2023-46195 WordPress Headline Analyzer plugin <= 1.3.1 - Broken Access Control vulnerability — Headline Analyzer 6.5 Medium 2025-01-02
CVE-2023-46188 WordPress Freesoul Deactivate Plugins plugin <= 2.1.3 - Broken Access Control vulnerability — Freesoul Deactivate Plugins – Plugin manager and cleanup 4.3 Medium 2025-01-02
CVE-2023-46083 WordPress Kali Forms plugin <= 2.3.27 - Broken Access Control vulnerability — Kali Forms 5.3 Medium 2025-01-02
CVE-2023-46082 WordPress Broken Link Checker | Finder plugin <= 2.4.2 - Broken Access Control vulnerability — Broken Link Checker | Finder 5.3 Medium 2025-01-02
CVE-2023-46080 WordPress ApplyOnline – Application Form Builder and Manager plugin <= 2.5.3 - Broken Access Control vulnerability — ApplyOnline – Application Form Builder and Manager 4.3 Medium 2025-01-02
CVE-2023-46073 WordPress DX Delete Attached Media plugin <= 2.0.5.1 - Broken Access Control vulnerability + CSRF — DX Delete Attached Media 5.3 Medium 2025-01-02
CVE-2023-46079 WordPress Ashe Extra plugin <= 1.2.9 - Broken Access Control + CSRF vulnerability — Ashe Extra 5.4 Medium 2025-01-02
CVE-2023-45828 WordPress RumbleTalk Live Group Chat plugin <= 6.2.5 - Broken Access Control vulnerability — RumbleTalk Live Group Chat 5.4 Medium 2025-01-02

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