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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

5581 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)
ConfidentialityRead 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.
IntegrityModify 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 ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
AvailabilityDoS: 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 DesignDivide 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 DesignEnsure 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 DesignUse 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 DesignFor 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, InstallationUse 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 IDTitleCVSSSeverityPublished
CVE-2026-1948 NEX-Forms – Ultimate Forms Plugin for WordPress <= 9.1.9 - Missing Authorization to Authenticated (Subscriber+) License Deactivation via deactivate_license — NEX-Forms – Ultimate Forms Plugin for WordPress 4.3 Medium2026-03-14
CVE-2026-32487 WordPress Lawyer Landing Page theme <= 1.2.7 - Broken Access Control vulnerability — Lawyer Landing Page 5.3 Medium2026-03-13
CVE-2026-32486 WordPress Travel Booking theme <= 1.3.9 - Broken Access Control vulnerability — Travel Booking 5.3 Medium2026-03-13
CVE-2026-32543 WordPress Responsive Blocks plugin <= 2.2.0 - Broken Access Control vulnerability — Responsive Blocks 5.3 Medium2026-03-13
CVE-2026-32461 WordPress Really Simple SSL plugin <= 9.5.7 - Broken Access Control vulnerability — Really Simple SSL 4.3 Medium2026-03-13
CVE-2026-32457 WordPress Advanced Product Fields (Product Addons) for WooCommerce plugin <= 1.6.18 - Broken Access Control vulnerability — Advanced Product Fields (Product Addons) for WooCommerce 5.3 Medium2026-03-13
CVE-2026-32453 WordPress Avada Core plugin < 5.15.0 - Broken Access Control vulnerability — Avada Core 5.3 Medium2026-03-13
CVE-2026-32452 WordPress Fusion Builder plugin < 3.15.0 - Broken Access Control vulnerability — Fusion Builder 5.3 Medium2026-03-13
CVE-2026-32446 WordPress Contact Form by WPForms plugin <= 1.9.9.3 - Broken Access Control vulnerability — Contact Form by WPForms 4.3 Medium2026-03-13
CVE-2026-32451 WordPress Fusion Builder plugin < 3.15.0 - Broken Access Control vulnerability — Fusion Builder 6.5 Medium2026-03-13
CVE-2026-32447 WordPress Atarim plugin <= 4.3.2 - Broken Access Control vulnerability — Atarim 4.3 Medium2026-03-13
CVE-2026-32439 WordPress BigHearts theme <= 3.1.14 - Broken Access Control vulnerability — BigHearts 5.3 Medium2026-03-13
CVE-2026-32442 WordPress e2pdf plugin <= 1.28.15 - Broken Access Control vulnerability — e2pdf 5.0 Medium2026-03-13
CVE-2026-32445 WordPress Elementor Website Builder plugin <= 3.35.5 - Broken Access Control vulnerability — Elementor Website Builder 2.7 Low2026-03-13
CVE-2026-32440 WordPress WP Food plugin < 2.7.1 - Broken Access Control vulnerability — WP Food 5.3 Medium2026-03-13
CVE-2026-32435 WordPress VW Pet Shop theme <= 1.4.7 - Broken Access Control vulnerability — VW Pet Shop 5.3 Medium2026-03-13
CVE-2026-32437 WordPress VW Portfolio theme <= 1.3.3 - Broken Access Control vulnerability — VW Portfolio 5.3 Medium2026-03-13
CVE-2026-32438 WordPress VW School Education theme <= 1.4.6 - Broken Access Control vulnerability — VW School Education 5.3 Medium2026-03-13
CVE-2026-32434 WordPress VW Fitness theme <= 4.3.4 - Broken Access Control vulnerability — VW Fitness 5.3 Medium2026-03-13
CVE-2026-32436 WordPress VW Photography theme <= 1.3.8 - Broken Access Control vulnerability — VW Photography 5.3 Medium2026-03-13
CVE-2026-32428 WordPress Popup Like box plugin <= 3.7.7 - Broken Access Control vulnerability — Popup Like box 5.3 Medium2026-03-13
CVE-2026-32432 WordPress WP Time Slots Booking Form plugin <= 1.2.42 - Broken Access Control vulnerability — WP Time Slots Booking Form 5.3 Medium2026-03-13
CVE-2026-32427 WordPress VW Education Lite plugin <= 2.2.0 - Broken Access Control vulnerability — VW Education Lite 5.3 Medium2026-03-13
CVE-2026-32423 WordPress Admin and Site Enhancements (ASE) plugin <= 8.4.0 - Broken Access Control vulnerability — Admin and Site Enhancements (ASE) 5.4 Medium2026-03-13
CVE-2026-32425 WordPress Payment Gateway Pix For GiveWP plugin <= 2.2.3 - Broken Access Control vulnerability — Payment Gateway Pix For GiveWP 5.3 Medium2026-03-13
CVE-2026-32417 WordPress Pochipp plugin < 1.18.9 - Broken Access Control vulnerability — Pochipp 5.4 Medium2026-03-13
CVE-2026-32421 WordPress Post Timeline plugin <= 2.4.1 - Broken Access Control vulnerability — Post Timeline 5.3 Medium2026-03-13
CVE-2026-32416 WordPress PDF Poster plugin <= 2.4.0 - Broken Access Control vulnerability — PDF Poster 5.4 Medium2026-03-13
CVE-2026-32413 WordPress Permalink Manager Lite plugin < 2.5.3 - Broken Access Control vulnerability — Permalink Manager Lite 5.3 Medium2026-03-13
CVE-2026-32409 WordPress Forminator plugin <= 1.50.2 - Broken Access Control vulnerability — Forminator 5.3 Medium2026-03-13

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