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-44052 WordPress HelloAsso plugin <= 1.1.10 - Broken Access Control vulnerability — HelloAsso 4.3 Medium 2024-11-01
CVE-2024-47308 WordPress Templately plugin <= 3.1.2 - Broken Access Control vulnerability — Templately 6.5 Medium 2024-11-01
CVE-2024-47317 WordPress Ads by WPQuads plugin <= 2.0.84 - Broken Access Control vulnerability — Ads by WPQuads 4.3 Medium 2024-11-01
CVE-2024-47318 WordPress PWA for WP & AMP plugin <= 1.7.72 - Broken Access Control vulnerability — PWA for WP & AMP 4.3 Medium 2024-11-01
CVE-2024-47321 WordPress WP Datepicker plugin <= 2.1.1 - Broken Access Control vulnerability — WP Datepicker 6.5 Medium 2024-11-01
CVE-2024-47358 WordPress Popup Maker plugin <= 1.19.2 - Broken Access Control vulnerability — Popup Maker 5.3 Medium 2024-11-01
CVE-2024-47361 WordPress Elementor Addon Elements plugin <= 1.13.6 - Broken Access Control vulnerability — Elementor Addon Elements 6.5 Medium 2024-11-01
CVE-2024-47362 WordPress Strong Testimonials plugin <= 3.1.16 - Broken Access Control vulnerability — Strong Testimonials 4.3 Medium 2024-11-01
CVE-2024-37094 WordPress MasterStudy LMS plugin <= 3.2.12 - Broken Access Control vulnerability — MasterStudy LMS 8.2 High 2024-11-01
CVE-2024-10399 Download Monitor <= 5.0.13 - Missing Authorization to Sensitive Information Exposure — Download Monitor 4.3 Medium 2024-10-30
CVE-2024-50421 WordPress PDF Invoices & Packing Slips for WooCommerce plugin <= 3.8.6 - Broken Access Control vulnerability — WooCommerce PDF Invoices & Packing Slips 5.3 Medium 2024-10-29
CVE-2024-50422 WordPress Breeze plugin <= 2.1.14 - Broken Access Control vulnerability — Breeze 5.3 Medium 2024-10-29
CVE-2024-50423 WordPress Templately plugin <= 3.1.5 - Broken Access Control vulnerability — Templately 5.4 Medium 2024-10-29
CVE-2024-50424 WordPress Templately plugin <= 3.1.5 - Broken Access Control vulnerability — Templately 6.5 Medium 2024-10-29
CVE-2024-50428 WordPress Multi Step Form plugin <= 1.7.21 - Broken Access Control vulnerability — Multi Step Form 4.3 Medium 2024-10-29
CVE-2024-50454 WordPress SEOPress plugin <= 8.1.1 - Unauthenticated Broken Access Control vulnerability — SEOPress 5.3 Medium 2024-10-29
CVE-2024-50455 WordPress SEOPress plugin <= 8.1.1 - Broken Access Control vulnerability — SEOPress 4.3 Medium 2024-10-29
CVE-2024-50456 WordPress SEOPress plugin <= 8.1.1 - Broken Access Control vulnerability — SEOPress 5.4 Medium 2024-10-29
CVE-2024-50459 WordPress AidWP plugin <= 3.2.3 - Broken Access Control vulnerability — AidWP 5.3 Medium 2024-10-29
CVE-2024-7475 Improper Access Control in lunary-ai/lunary — lunary-ai/lunary 7.5AI High AI 2024-10-29
CVE-2024-10437 WPC Smart Messages for WooCommerce <= 4.2.1 - Missing Authorization to Authenticated (Subscriber+) Message Activation/Deactivation — WPC Smart Messages for WooCommerce 4.3 Medium 2024-10-29
CVE-2024-50475 WordPress Signup Page plugin <= 1.0 - Arbitrary Option Update to Privilege Escalation vulnerability — Signup Page 9.8 Critical 2024-10-29
CVE-2024-50476 WordPress GRÜN spendino Spendenformular plugin <= 1.0.1 - Arbitrary Option Update to Privilege Escalation vulnerability — GRÜN spendino Spendenformular 9.8 Critical 2024-10-29
CVE-2024-50490 WordPress PegaPoll plugin <= 1.0.2 - Arbitrary Option Update to Privilege Escalation vulnerability — PegaPoll 9.8 Critical 2024-10-29
CVE-2024-50052 Arbitrary post deletion via Playbooks /ignore-thread endpoint — Mattermost 4.3 Medium 2024-10-29
CVE-2024-10008 Masteriyo LMS – eLearning and Online Course Builder for WordPress <= 1.13.3 - Authenticated (Student+) Missing Authorization to Privilege Escalation — Masteriyo LMS – Online Course Builder for eLearning, LMS & Education 8.8 High 2024-10-29
CVE-2024-9629 Contact Form 7 + Telegram <= 0.8.5 - Missing Authorization to Authenticated (Subscriber+) Subscription Approve/Pause/Refuse — Message Bridge for Contact Form 7 and Telegram 5.4 Medium 2024-10-28
CVE-2024-50573 JetBrains Hub 安全漏洞 — Hub 4.3 Medium 2024-10-28
CVE-2024-10402 Forminator Forms – Contact Form, Payment Form & Custom Form Builder <= 1.35.1 - Missing Authorization to Authenticated (Contributor+) Form Update and Creation — Forminator Forms – Contact Form, Payment Form & Custom Form Builder 7.5 High 2024-10-26
CVE-2024-10092 Download Monitor <= 5.0.12 - Missing Authorization to API Key Manipulation — Download Monitor 4.3 Medium 2024-10-26

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