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-31886 WordPress Social proof testimonials and reviews by Repuso plugin <= 5.21 - Broken Access Control vulnerability — Social proof testimonials and reviews by Repuso 4.3 Medium 2025-04-01
CVE-2025-31882 WordPress Webinar Plugin <= 1.33.28 - Broken Access Control vulnerability — WebinarPress 4.3 Medium 2025-04-01
CVE-2025-31881 WordPress Pearl plugin <= 1.3.9 - Broken Access Control vulnerability — Pearl 5.4 Medium 2025-04-01
CVE-2025-31879 WordPress Barcode Generator for WooCommerce plugin <= 2.0.4 - Settings Change vulnerability — Barcode Generator for WooCommerce 5.4 Medium 2025-04-01
CVE-2025-31878 WordPress UPC/EAN/GTIN Code Generator plugin <= 2.0.2 - Settings Change vulnerability — UPC/EAN/GTIN Code Generator 5.4 Medium 2025-04-01
CVE-2025-31877 WordPress RestroPress plugin <= 3.2.8 - Broken Access Control vulnerability — RestroPress 4.3 Medium 2025-04-01
CVE-2025-31872 WordPress WP Clone any post type Plugin <= 3.6 - Broken Access Control vulnerability — WP Clone any post type 5.3 Medium 2025-04-01
CVE-2025-31870 WordPress WP AutoKeyword plugin <= 1.0 - Arbitrary Content Deletion vulnerability — WP AutoKeyword 5.4 Medium 2025-04-01
CVE-2025-31868 WordPress JS Job Manager plugin <= 2.0.2 - Broken Access Control vulnerability — JS Job Manager 5.3 Medium 2025-04-01
CVE-2025-31866 WordPress ShipDepot for WooCommerce plugin <= 1.2.19 - Broken Access Control vulnerability — ShipDepot for WooCommerce 4.3 Medium 2025-04-01
CVE-2025-31865 WordPress CartBoss plugin <= 4.1.2 - Broken Access Control vulnerability — CartBoss 4.3 Medium 2025-04-01
CVE-2025-31863 WordPress Agency Toolkit plugin <= 1.0.24 - Broken Access Control vulnerability — Agency Toolkit 5.3 Medium 2025-04-01
CVE-2025-31862 WordPress Job Board Manager Plugin <= 2.1.61 - Broken Access Control vulnerability — Job Board Manager 5.3 Medium 2025-04-01
CVE-2025-31856 WordPress Export All Post Meta Plugin <= 1.2.1 - Broken Access Control vulnerability — Export All Post Meta 4.3 Medium 2025-04-01
CVE-2025-31854 WordPress Simple Sticky Add To Cart For WooCommerce plugin <= 1.4.9 - Broken Access Control vulnerability — Simple Sticky Add To Cart For WooCommerce 4.3 Medium 2025-04-01
CVE-2025-31848 WordPress WordPress Adverts Plugin plugin <= 1.4 - Broken Access Control vulnerability — Adverts 5.3 Medium 2025-04-01
CVE-2025-31846 WordPress Theater for WordPress plugin <= 0.18.7 - Broken Access Control vulnerability — Theater for WordPress 4.3 Medium 2025-04-01
CVE-2025-31843 WordPress OpenAI Tools for WordPress & WooCommerce plugin <= 2.2.1 - Broken Access Control vulnerability — OpenAI Tools for WordPress & WooCommerce 4.3 Medium 2025-04-01
CVE-2025-31836 WordPress Review Manager plugin <= 2.5.0 - Broken Access Control vulnerability — Review Manager 5.3 Medium 2025-04-01
CVE-2025-31834 WordPress JobBoard Job listing plugin Plugin <= 1.2.8 - Broken Access Control vulnerability — JobBoard Job listing 5.3 Medium 2025-04-01
CVE-2025-31830 WordPress Printus Plugin <= 1.2.6 - Broken Access Control vulnerability — Printus 4.3 Medium 2025-04-01
CVE-2025-31831 WordPress AtomChat plugin <= 1.1.7 - Broken Access Control vulnerability — AtomChat 4.3 Medium 2025-04-01
CVE-2025-31826 WordPress Ni WooCommerce Cost Of Goods plugin <= 3.2.8 - Broken Access Control vulnerability — Ni WooCommerce Cost Of Goods 5.4 Medium 2025-04-01
CVE-2025-31822 WordPress WordPress Simple HTML Sitemap plugin <= 3.4 - Broken Access Control vulnerability — WP Simple HTML Sitemap 5.3 Medium 2025-04-01
CVE-2025-31820 WordPress Automatic Featured Images from Videos plugin <= 1.2.4 - Broken Access Control vulnerability — Automatic Featured Images from Videos 4.3 Medium 2025-04-01
CVE-2025-31816 WordPress Mobile App Canvas Plugin <= 3.8.2 - Broken Access Control vulnerability — Mobile App Canvas 5.4 Medium 2025-04-01
CVE-2025-31810 WordPress Question Answer plugin <= 1.2.73 - Broken Access Control vulnerability — Question Answer 5.3 Medium 2025-04-01
CVE-2025-31802 WordPress Shiptimize for WooCommerce plugin <= 3.1.86 - Settings Change vulnerability — Shiptimize for WooCommerce 5.4 Medium 2025-04-01
CVE-2025-31799 WordPress Publitio plugin <= 2.1.8 - Broken Access Control vulnerability — Publitio 4.3 Medium 2025-04-01
CVE-2025-31798 WordPress Publitio Plugin <= 2.1.8 - Broken Access Control vulnerability — Publitio 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.