目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1325

100%

CWE-862 授权机制缺失 类漏洞列表 5967

CWE-862 授权机制缺失 类弱点 5967 条 CVE 漏洞汇总,含 AI 中文分析。

CWE-862 属于缺失授权漏洞,指产品在用户访问资源或执行操作时未进行权限校验。攻击者通常通过直接修改请求参数或构造恶意 URL,绕过前端限制以访问未授权数据或执行敏感操作。开发者应避免仅依赖前端验证,需在服务端对每个请求实施严格的身份认证与权限检查,确保用户仅能访问其被授权的资源,从而从根本上消除越权风险。

MITRE CWE 官方描述
CWE:CWE-862 Missing Authorization(缺失授权) 英文:当主体尝试访问资源或执行操作时,产品未执行授权检查。
常见影响 (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.
缓解措施 (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.
代码示例 (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标题CVSS风险等级Published
CVE-2026-54802 Cozy Vision Technologies Pvt. Ltd SMS Alert Order Notifications 授权问题漏洞 — SMS Alert Order Notifications 7.5 High2026-06-17
CVE-2026-49081 WordPress用户注册Stripe插件<=1.3.12越权访问漏洞 — User Registration Stripe 8.2 High2026-06-17
CVE-2026-49072 WordPress WooCommerce Anti-Fraud插件 <= 7.2.6 访问控制漏洞 — WooCommerce Anti-Fraud 6.5 Medium2026-06-17
CVE-2026-45436 WordPress WPBakery Page Builder <= 8.7.2 访问控制漏洞 — WPBakery Page Builder 6.5 Medium2026-06-17
CVE-2026-40726 WordPress User Registration Stripe插件 <= 1.3.14 访问控制漏洞 — User Registration Stripe 8.2 High2026-06-17
CVE-2026-40723 WordPress Bricks Builder主题 <= 2.1.4 访问控制漏洞 — Bricks Builder 4.3 Medium2026-06-17
CVE-2026-39595 WordPress W3 Total Cache插件 <= 2.9.1 访问控制漏洞 — W3 Total Cache 4.7 Medium2026-06-17
CVE-2026-24611 WordPress MetForm Pro <=3.9.1 权限控制漏洞 — MetForm Pro 9.1 Critical2026-06-17
CVE-2026-24610 WordPress MetForm Pro <= 3.9.1 访问控制漏洞 — MetForm Pro 4.3 Medium2026-06-17
CVE-2026-24575 WordPress WishList Member X插件 <= 3.29.0 访问控制漏洞 — WishList Member X 4.3 Medium2026-06-17
CVE-2026-22343 WordPress Dating Theme 主题 <=11.2.0 权限控制漏洞 — WordPress Dating Theme 8.6 High2026-06-17
CVE-2026-40722 WordPress Yoast SEO Premium <= 26.6 越权漏洞 — Yoast SEO Premium 5.5 Medium2026-06-17
CVE-2026-49057 WordPress JobSearch插件<=3.2.7 访问控制漏洞 — JobSearch 7.5 High2026-06-16
CVE-2026-39433 WordPress WPAMS插件 < 49.5.3 任意内容删除漏洞 — WPAMS 6.5 Medium2026-06-16
CVE-2025-69137 WordPress Genemy主题<=1.6.6 访问控制漏洞 — Genemy 6.5 Medium2026-06-16
CVE-2025-69103 Utillz Brikk 授权问题漏洞 — Brikk 7.5 High2026-06-16
CVE-2026-12105 Devolutions Server 授权问题漏洞 — Devolutions Server--2026-06-16
CVE-2026-53866 OpenClaw < 2026.5.12 Shell内联命令解析白名单绕过漏洞 — OpenClaw 8.1 High2026-06-16
CVE-2026-53851 OpenClaw < 2026.5.12 Slack反应事件通知绕过漏洞 — OpenClaw 5.3 Medium2026-06-16
CVE-2026-53850 OpenClaw < 2026.4.25 焦点命令控制范围绕过漏洞 — OpenClaw 5.5 Medium2026-06-16
CVE-2026-53844 OpenClaw < 2026.4.29 共享内存搜索会话可见性检查绕过漏洞 — OpenClaw 6.5 Medium2026-06-16
CVE-2025-14272 Rockwell FactoryTalk Analytics PavilionX 安全漏洞 — FactoryTalk Analytics PavilionX--2026-06-16
CVE-2026-10831 设备中断信号命令不当授权漏洞 — NPort 6000 Series--2026-06-16
CVE-2026-2381 WooCommerce Stripe Payment Gateway <=10.7.0 身份验证缺失导致订单状态被篡改漏洞 — WooCommerce Stripe Payment Gateway 6.5 Medium2026-06-16
CVE-2026-40809 WordPress Metro Magazine主题1.4.1及更早版本访问控制漏洞 — Metro Magazine 6.5 Medium2026-06-16
CVE-2026-54190 WordPress Envira Photo Gallery插件 <= 1.12.5 访问控制漏洞 — Envira Photo Gallery 6.5 Medium2026-06-16
CVE-2026-52714 WordPress Squirrly SEO插件 <=12.4.16 访问控制漏洞 — SEO Plugin by Squirrly SEO 7.5 Medium2026-06-16
CVE-2026-52711 WordPress WooCommerce POS <= 1.8.14 访问控制漏洞 — WooCommerce POS 7.5 High2026-06-16
CVE-2026-39490 WordPress JupiterX Core 插件 <= 4.14.1 访问控制漏洞 — JupiterX Core 7.5 High2026-06-16
CVE-2025-68045 WordPress WP Event Solution 插件<=4.1.12 访问控制漏洞 — WP Event SOlution 7.5 High2026-06-16

CWE-862(授权机制缺失) 是常见的弱点类别,本平台收录该类弱点关联的 5967 条 CVE 漏洞。