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-31584 WordPress Elfsight Testimonials Slider plugin <= 1.0.1 - Broken Access Control vulnerability — Elfsight Testimonials Slider 5.4 Medium 2025-03-31
CVE-2025-31576 WordPress PostmarkApp Email Integrator plugin <= 2.4 - Broken Access Control vulnerability — PostmarkApp Email Integrator 4.3 Medium 2025-03-31
CVE-2025-31555 WordPress ContentMX Content Publisher plugin <= 1.0.6 - Broken Access Control vulnerability — ContentMX Content Publisher 5.4 Medium 2025-03-31
CVE-2025-31546 WordPress Swiss Toolkit For WP plugin <= 1.4.0 - Broken Access Control vulnerability — Swiss Toolkit For WP 4.3 Medium 2025-03-31
CVE-2025-31545 WordPress Safe Ai Malware Protection for WP plugin <= 1.0.20 - Broken Access Control vulnerability — Safe Ai Malware Protection for WP 5.4 Medium 2025-03-31
CVE-2025-31544 WordPress Swiss Toolkit For WP plugin <= 1.4.5 - Broken Access Control vulnerability — Swiss Toolkit For WP 4.3 Medium 2025-03-31
CVE-2025-31540 WordPress ACME Divi Modules plugin <= 1.3.5 - Broken Access Control vulnerability — ACME Divi Modules 4.3 Medium 2025-03-31
CVE-2025-31539 WordPress Cryptocurrency Widgets Pack plugin <= 2.0.1 - Broken Access Control vulnerability — Cryptocurrency Widgets Pack 6.5 Medium 2025-03-31
CVE-2025-31533 WordPress Salesmate Add-On for Gravity Forms plugin <= 2.0.3 - Broken Access Control vulnerability — Salesmate Add-On for Gravity Forms 5.3 Medium 2025-03-31
CVE-2025-31529 WordPress Slider Path for Elementor plugin <= 3.0.0 - Broken Access Control vulnerability — Slider Path for Elementor 4.3 Medium 2025-03-31
CVE-2025-31530 WordPress Google SEO Pressor Snippet plugin <= 2.0 - Broken Access Control vulnerability — Google SEO Pressor Snippet 4.3 Medium 2025-03-31
CVE-2025-31528 WordPress StaticPress plugin <= 0.4.5 - Broken Access Control vulnerability — StaticPress 4.3 Medium 2025-03-31
CVE-2025-31376 WordPress NanoSupport plugin <= 0.6.0 - Broken Access Control vulnerability — NanoSupport 4.3 Medium 2025-03-31
CVE-2025-31386 WordPress Simple:Press plugin <= 6.11.5 - Broken Access Control vulnerability — Simple:Press 5.3 Medium 2025-03-31
CVE-2025-31406 WordPress ELEX WooCommerce Request a Quote plugin <= 2.3.9 - Broken Access Control vulnerability — ELEX WooCommerce Request a Quote 4.3 Medium 2025-03-31
CVE-2025-30855 WordPress Ads by WPQuads plugin <= 2.0.87.1 - Broken Access Control Vulnerability — Ads by WPQuads 7.5 High 2025-03-31
CVE-2025-31417 WordPress WP Docs plugin < 2.2.7 - Broken Access Control vulnerability — WP Docs 4.3 Medium 2025-03-31
CVE-2025-2266 Checkout Mestres do WP for WooCommerce 8.6.5 - 8.7.5 - Unauthenticated Arbitrary Options Update — Checkout Mestres do WP for WooCommerce 9.8 Critical 2025-03-29
CVE-2025-31469 WordPress Clear Sucuri Cache plugin <= 1.4 - Broken Access Control Vulnerability — Clear Sucuri Cache 5.3 Medium 2025-03-28
CVE-2025-2815 Administrator Z <= 2025.03.24 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Options Update — Administrator Z 8.8 High 2025-03-28
CVE-2025-26733 WordPress Traveler theme < 3.2.1 - Broken Access Control vulnerability — Traveler 8.2 High 2025-03-27
CVE-2025-26956 WordPress Traveler theme < 3.2.1 - Broken Access Control vulnerability — Traveler 7.6 High 2025-03-27
CVE-2025-22739 WordPress LearnPress plugin <= 4.2.7.5 - Broken Access Control vulnerability — LearnPress 5.3 Medium 2025-03-27
CVE-2025-22740 WordPress Sensei LMS plugin <= 4.24.4 - Broken Access Control vulnerability — Sensei LMS 5.3 Medium 2025-03-27
CVE-2025-22629 WordPress iNET Webkit Plugin <= 1.2.2 - Broken Access Control vulnerability — iNET Webkit 5.3 Medium 2025-03-27
CVE-2025-22647 WordPress AIO Performance Profiler plugin <= 1.2 - Broken Access Control vulnerability — AIO Performance Profiler, Monitor, Optimize, Compress & Debug 4.3 Medium 2025-03-27
CVE-2025-22665 WordPress RapidLoad plugin <= 2.4.4 - Broken Access Control vulnerability — RapidLoad 4.3 Medium 2025-03-27
CVE-2025-22667 WordPress Export Order, Product, Customer & Coupon for WooCommerce to Google Sheets plugin <= 1.8.2 - Broken Access Control vulnerability — Export Order, Product, Customer & Coupon for WooCommerce to Google Sheets 4.3 Medium 2025-03-27
CVE-2025-22668 WordPress Awesome Event Booking plugin <= 2.7.2 - Broken Access Control vulnerability — Awesome Event Booking 6.5 Medium 2025-03-27
CVE-2025-22670 WordPress VikBooking Hotel Booking Engine & PMS plugin <= 1.7.2 - CSRF to Settings Change vulnerability — VikBooking Hotel Booking Engine & PMS 6.5 Medium 2025-03-27

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