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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

8303 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-2026-25267 Missing Authorization in Core — Snapdragon 7.8 High 2026-10-06
CVE-2026-39789 WordPress Fluent Affiliate Pro plugin <= 1.6.4 - Broken Access Control vulnerability — Fluent Affiliate Pro 7.5 High 2026-10-06
CVE-2026-39723 WordPress Morning for WooCommerce plugin <= 2.4.1 - Broken Access Control vulnerability — Morning for WooCommerce 7.5 High 2026-10-06
CVE-2026-39599 WordPress WDS MCP Content Manager plugin <= 3.10.4 - Broken Access Control vulnerability — WDS MCP Content Manager 4.3 Medium 2026-10-06
CVE-2026-32582 WordPress IATO MCP plugin <= 1.12.0 - Broken Access Control vulnerability — IATO MCP 6.5 Medium 2026-10-06
CVE-2026-105072 WordPress FluentBooking Pro plugin < 2.5.0 - Broken Access Control vulnerability — FluentBooking Pro 7.5 High 2026-10-06
CVE-2026-103433 Bake filesystem entitlement consent is skipped for certain secret and oci-layout definitions — Docker Buildx 6.9 Medium 2026-10-05
CVE-2026-105696 Penpot: Share-link page-scope escalation: a share-link holder reads pages outside the link's authorized scope via the get-page RPC command — penpot 6.5 Medium 2026-10-05
CVE-2026-105695 Penpot: Missing authorization in chunked-upload assembly lets another authenticated user consume a victim's upload session — penpot 5.9 Medium 2026-10-05
CVE-2026-105693 Penpot: Anonymous share-link token disclosure & page-scope bypass via get-view-only-bundle — penpot 5.3 Medium 2026-10-05
CVE-2026-105680 Ghost: Authorization Issue Allowed Author Role to Delete any Post — Ghost 6.5 Medium 2026-10-05
CVE-2026-103337 WordPress WC Ukraine Shipping plugin <= 1.23.2 - Broken Access Control vulnerability — WC Ukraine Shipping 6.5 Medium 2026-10-05
CVE-2026-97303 WordPress Scratch & Win – Giveaways and Contests plugin <= 3.0.2 - Broken Access Control vulnerability — Scratch & Win – Giveaways and Contests 7.6 High 2026-10-05
CVE-2026-97309 WordPress RepairBuddy plugin <= 4.1226 - Sensitive Data Exposure vulnerability — RepairBuddy 7.1 High 2026-10-05
CVE-2026-103086 WordPress UsersWP plugin <= 1.2.74 - Broken Access Control vulnerability — UsersWP 6.5 Medium 2026-10-05
CVE-2026-97304 WordPress Timetics plugin <= 1.0.63 - Broken Access Control vulnerability — Timetics 6.5 Medium 2026-10-05
CVE-2026-102383 WordPress Lookzy plugin <= 1.1.14 - Broken Access Control vulnerability — Lookzy 6.5 Medium 2026-10-05
CVE-2026-104968 Plane: Cross-workspace member enumeration via /api/workspaces/{slug}/entity-search/ — plane 8.7 High 2026-10-05
CVE-2026-104962 Plane: Cross-project member roster IDOR in ProjectMemberListCreateAPIEndpoint (missing project scope on reads) — plane 6.5 Medium 2026-10-05
CVE-2026-102779 Joomla Extension - joomlafry.com - Unauthenticated forced execution of published automation tasks in TF Content 2.9.0 - 2.9.4 — TF Content for Joomla 6.9 Medium 2026-10-05
CVE-2026-102780 Joomla Extension - joomlafry.com - Unauthenticated cross-record publication and mass assignment in TF Content 2.9.0 - 2.9.4 — TF Content for Joomla 6.9 Medium 2026-10-05
CVE-2026-105421 WordPress Kit (formerly ConvertKit) for WooCommerce plugin <= 2.2.0 - Broken Access Control vulnerability — Kit (formerly ConvertKit) for WooCommerce 5.3 Medium 2026-10-05
CVE-2026-39783 WordPress Polylang plugin <= 3.8.7 - Sensitive Data Exposure vulnerability — Polylang 4.3 Medium 2026-10-05
CVE-2026-103684 WordPress WP Event Solution plugin <= 4.1.25 - Broken Access Control vulnerability — WP Event Solution 5.3 Medium 2026-10-05
CVE-2026-94669 WordPress Fluent Forms Pro Add On Pack plugin <= 6.2.13 - Broken Access Control vulnerability — Fluent Forms Pro Add On Pack 5.3 Medium 2026-10-05
CVE-2026-39763 WordPress WP Dummy Content Generator plugin <= 4.0.0 - Broken Access Control vulnerability — WP Dummy Content Generator 4.3 Medium 2026-10-05
CVE-2026-39721 WordPress Starter Templates plugin <= 4.7.7 - Broken Access Control vulnerability — Starter Templates 5.4 Medium 2026-10-05
CVE-2026-104388 WordPress PowerPress Podcasting plugin <= 11.17.9 - Sensitive Data Exposure vulnerability — PowerPress Podcasting 5.3 Medium 2026-10-05
CVE-2026-104675 WordPress Event Tickets plugin <= 5.30.0 - Broken Access Control vulnerability — Event Tickets 4.3 Medium 2026-10-05
CVE-2026-104397 WordPress Name Directory plugin <= 1.34.2 - Arbitrary Shortcode Execution vulnerability — Name Directory 5.3 Medium 2026-10-05

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