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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

6902 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-2024-43310 WordPress Print Labels with Barcodes. Create price tags, product labels, order labels for WooCommerce plugin <= 3.4.9 - Broken Access Control vulnerability — Print Barcode Labels for your WooCommerce products/orders 6.5 Medium 2024-11-01
CVE-2024-43312 WordPress WPC Frequently Bought Together for WooCommerce plugin <= 7.1.9 - Broken Access Control vulnerability — WPC Frequently Bought Together for WooCommerce 5.4 Medium 2024-11-01
CVE-2024-43314 WordPress Asset CleanUp: Page Speed Booster plugin <= 1.3.9.3 - Broken Access Control vulnerability — Asset CleanUp: Page Speed Booster 4.3 Medium 2024-11-01
CVE-2024-43323 WordPress ReviewX plugin <= 1.6.28 - Broken Access Control vulnerability — ReviewX 5.3 Medium 2024-11-01
CVE-2024-43341 WordPress Hello Agency theme <= 1.0.5 - Broken Access Control vulnerability — Hello Agency 6.5 Medium 2024-11-01
CVE-2024-43332 WordPress Photo Engine plugin <= 6.4.0 - Broken Access Control vulnerability — Photo Engine 4.3 Medium 2024-11-01
CVE-2024-43343 WordPress Order Tracking – WordPress Status Tracking Plugin plugin < 3.3.13 - Broken Access Control vulnerability — Order Tracking 4.3 Medium 2024-11-01
CVE-2024-43355 WordPress JoomSport plugin <= 5.3.0 - Broken Access Control vulnerability — JoomSport 4.3 Medium 2024-11-01
CVE-2024-43919 WordPress Yet Another Related Posts Plugin (YARPP) plugin <= 5.30.10 - Broken Access Control vulnerability — YARPP 5.3 Medium 2024-11-01
CVE-2024-43923 WordPress Timetics plugin <= 1.0.23 - Broken Access Control vulnerability — Timetics 5.3 Medium 2024-11-01
CVE-2024-43925 WordPress Envira Gallery Lite plugin <= 1.8.14 - Broken Access Control vulnerability — Envira Photo Gallery 4.3 Medium 2024-11-01
CVE-2024-43929 WordPress JobSearch WP Job Board WordPress Plugin plugin <= 2.5.4 - Broken Access Control vulnerability — JobSearch 6.5 Medium 2024-11-01
CVE-2024-43928 WordPress JobSearch WP Job Board WordPress Plugin plugin <= 2.5.4 - Broken Access Control vulnerability — JobSearch 5.4 Medium 2024-11-01
CVE-2024-43932 WordPress The Plus Addons for Elementor plugin <= 5.6.2 - Broken Access Control vulnerability — The Plus Addons for Elementor Page Builder Lite 6.5 Medium 2024-11-01
CVE-2024-43937 WordPress WP Crowdfunding plugin <= 2.1.10 - Settings Change vulnerability — WP Crowdfunding 6.4 Medium 2024-11-01
CVE-2024-43956 WordPress MemberPress plugin <= 1.11.34 - Broken Access Control vulnerability — Memberpress 6.5 Medium 2024-11-01
CVE-2024-43962 WordPress LWS Affiliation plugin <= 2.3.4 - Broken Access Control vulnerability — LWS Affiliation 5.4 Medium 2024-11-01
CVE-2024-43968 WordPress Newspack plugin < 3.8.7 - Broken Access Control vulnerability — Newspack 4.3 Medium 2024-11-01
CVE-2024-43973 WordPress GetPaid plugin <= 2.8.11 - Broken Access Control vulnerability — GetPaid 4.3 Medium 2024-11-01
CVE-2024-43979 WordPress Blockbooster theme <= 1.0.10 - Broken Access Control vulnerability — Blockbooster 6.5 Medium 2024-11-01
CVE-2024-43974 WordPress ReviveNews theme <= 1.0.2 - Broken Access Control vulnerability — ReviveNews 6.5 Medium 2024-11-01
CVE-2024-43980 WordPress FotaWP theme <= 1.4.1 - Broken Access Control vulnerability — Fota WP 6.5 Medium 2024-11-01
CVE-2024-43981 WordPress GeoDirectory plugin <= 2.3.70 - Broken Access Control vulnerability — GeoDirectory 4.3 Medium 2024-11-01
CVE-2024-43982 WordPress Login As Users plugin <= 1.4.3 - Broken Access Control to Account Takeover vulnerability — Login As Users 8.8 High 2024-11-01
CVE-2024-43998 WordPress Blogpoet theme <= 1.0.3 - Broken Access Control vulnerability — Blogpoet 6.5 Medium 2024-11-01
CVE-2024-44006 WordPress WooCommerce Multilingual & Multicurrency plugin <= 5.3.7 - Broken Access Control vulnerability — WooCommerce Multilingual & Multicurrency 4.3 Medium 2024-11-01
CVE-2024-44019 WordPress Contact Form 7 Campaign Monitor Extension plugin <= 0.4.67 - Arbitrary File Deletion vulnerability — Contact Form 7 Campaign Monitor Extension 5.3 Medium 2024-11-01
CVE-2024-44020 WordPress WP Free SSL plugin <= 1.2.6 - Broken Access Control vulnerability — WP Free SSL – Free SSL Certificate for WordPress and force HTTPS 4.3 Medium 2024-11-01
CVE-2024-44021 WordPress Truepush plugin <= 1.0.8 - Broken Access Control vulnerability — Truepush 5.4 Medium 2024-11-01
CVE-2024-44031 WordPress JoomSport plugin <= 5.6.3 - Broken Access Control vulnerability — JoomSport 4.3 Medium 2024-11-01

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