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-2025-22285 WordPress Pallet Packaging for WooCommerce Plugin <= 1.1.15 - Broken Access Control vulnerability — Pallet Packaging for WooCommerce 8.2 - 2025-04-04
CVE-2025-31381 WordPress Booking Calendar and Notification plugin <= 4.0.3 - Broken Authentication vulnerability — Booking Calendar and Notification 6.5 Medium 2025-04-04
CVE-2025-2075 Uncanny Automator <= 6.3.0.2 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation — Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin 8.8 High 2025-04-04
CVE-2025-31909 WordPress Apptivo Business Site CRM plugin <= 5.3 - Arbitrary Content Deletion vulnerability — Apptivo Business Site CRM 7.5 High 2025-04-03
CVE-2025-31896 WordPress GetBookingsWP Plugin <= 1.1.27 - Broken Access Control vulnerability — GetBookingsWP 6.5 Medium 2025-04-03
CVE-2025-31841 WordPress FPW Category Thumbnails Plugin <= 1.9.5 - Broken Access Control vulnerability — FPW Category Thumbnails 6.3 Medium 2025-04-03
CVE-2025-31876 WordPress Payday plugin <= 3.3.18 - Broken Access Control vulnerability — Payday 5.8 Medium 2025-04-03
CVE-2025-31858 WordPress Local Magic plugin <= 2.9.0 - Broken Access Control vulnerability — Local Magic 6.5 Medium 2025-04-03
CVE-2025-31794 WordPress WR Price List Manager For Woocommerce plugin <= 1.0.8 - Arbitrary Content Deletion vulnerability — WR Price List Manager For Woocommerce 5.4 Medium 2025-04-03
CVE-2025-31768 WordPress Widget Manager Light plugin <= 1.18 - Broken Access Control vulnerability — Widget Manager Light 6.5 Medium 2025-04-03
CVE-2025-31789 WordPress TextMe SMS plugin <= 1.9.1 - Broken Access Control vulnerability — TextMe SMS 6.5 Medium 2025-04-03
CVE-2025-31795 WordPress Shopify to WooCommerce Migration plugin <= 1.3.0 - Settings Change vulnerability — Shopify to WooCommerce Migration 6.5 Medium 2025-04-03
CVE-2025-31746 WordPress Clients plugin <= 1.1.4 - Broken Access Control vulnerability — Clients 6.4 Medium 2025-04-03
CVE-2025-31736 WordPress Rich Text Editor Plugin <= 1.0.1 - Broken Access Control vulnerability — Rich Text Editor 6.5 Medium 2025-04-03
CVE-2025-31758 WordPress Free Woocommerce Product Table View plugin <= 1.78 - Arbitrary Content Deletion vulnerability — Free Woocommerce Product Table View 6.5 Medium 2025-04-03
CVE-2025-31739 WordPress Minimalistic Event Manager plugin <= 1.1.1 - Broken Access Control vulnerability — Minimalistic Event Manager 6.4 Medium 2025-04-03
CVE-2025-31729 WordPress WooTumblog plugin <= 2.1.4 - Content Injection vulnerability — WooTumblog 6.5 Medium 2025-04-03
CVE-2025-31581 WordPress WP Video Playlist plugin <= 1.1.2 - Settings Change vulnerability — WP Video Playlist 6.5 Medium 2025-04-03
CVE-2025-31541 WordPress TuriTop Booking System plugin <= 1.0.10 - Broken Access Control vulnerability — TuriTop Booking System 6.5 Medium 2025-04-03
CVE-2025-30916 WordPress Residential Address Detection plugin <= 2.5.4 - Broken Access Control vulnerability — Residential Address Detection 6.5 Medium 2025-04-03
CVE-2025-30915 WordPress Small Package Quotes – Worldwide Express Edition plugin <= 5.2.19 - Broken Access Control vulnerability — Small Package Quotes – Worldwide Express Edition 6.5 Medium 2025-04-03
CVE-2025-3063 Shopper Approved Reviews 2.0 - 2.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Options Update — Shopper Approved Reviews 8.8 High 2025-04-02
CVE-2024-13637 Demo Awesome <= 1.0.3 - Missing Authorization to Authenticated (Subscriber+) Plugin Activation — Demo Awesome 6.5 Medium 2025-04-02
CVE-2025-2779 Insert Headers and Footers Code – HT Script <= 1.1.2 - Missing Authorization to Authenticated (Subscriber+) Limited Options Update — Insert Headers and Footers Code – HT Script 6.5 Medium 2025-04-02
CVE-2025-31628 WordPress Sliced Invoices plugin <= 3.10.0 - Insecure Direct Object References (IDOR) vulnerability — Sliced Invoices 5.3 Medium 2025-04-01
CVE-2025-31580 WordPress Ni WooCommerce Product Enquiry plugin <= 4.1.8 - Broken Access Control vulnerability — Ni WooCommerce Product Enquiry 7.5 High 2025-04-01
CVE-2025-31525 WordPress WP Mobile Bottom Menu plugin <= 1.4.0 - Broken Access Control vulnerability — WP Mobile Bottom Menu 4.3 Medium 2025-04-01
CVE-2025-30853 WordPress ShortPixel Adaptive Images plugin <= 3.10.0 - Broken Authentication vulnerability — ShortPixel Adaptive Images 5.4 Medium 2025-04-01
CVE-2025-30825 WordPress WPC Smart Linked Products plugin <= 1.3.5 - Privilege Escalation vulnerability — WPC Smart Linked Products - Upsells & Cross-sells for WooCommerce 8.8 High 2025-04-01
CVE-2025-31887 WordPress MyBookProgress plugin <= 1.0.8 - Broken Access Control vulnerability — MyBookProgress by Stormhill Media 4.3 Medium 2025-04-01

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