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

目标: 1000 元 · 已筹: 1310

100%

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

CWE-862 授权机制缺失 类弱点 5804 条 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-31942 LibreChat API密钥管理越权修改漏洞 — LibreChat 7.1 High2026-06-02
CVE-2026-10616 GoClaw Team Task Completion 授权绕过漏洞 — GoClaw 4.3 Medium2026-06-02
CVE-2026-40571 NamelessMC 私聊或屏蔽帖子的回复可被未授权修改 — Nameless--2026-06-02
CVE-2026-40314 NamelessMC 私有/屏蔽帖子的互动可未授权读取和修改 — Nameless--2026-06-02
CVE-2026-35443 NamelessMC论坛反应绕过“仅查看自己主题”限制漏洞 — Nameless--2026-06-02
CVE-2026-49782 WordPress Elementor <= 4.1.0 访问控制漏洞 — Elementor Website Builder 5.4 Medium2026-06-02
CVE-2026-27351 WordPress Crew HRM插件<=1.2.2 访问控制漏洞 — Crew HRM 5.4 Medium2026-06-02
CVE-2026-42670 WordPress Five Star Restaurant Reservations插件 <= 2.7.14 支付绕过漏洞 — Five Star Restaurant Reservations--2026-06-02
CVE-2026-42669 WordPress EventPrime 插件 <= 4.3.2.0 访问控制缺陷漏洞 — EventPrime 7.5 High2026-06-02
CVE-2025-53346 WordPress Thim Core 插件 <=2.3.3 访问控制漏洞 — Thim Core 4.3 Medium2026-06-02
CVE-2025-53345 WordPress Thim Core插件<=2.3.3 任意代码执行漏洞 — Thim Core 8.8 High2026-06-02
CVE-2025-53302 WordPress Constructor 主题 <= 1.6.5 访问控制缺陷漏洞 — Constructor 5.3 Medium2026-06-02
CVE-2025-52766 WordPress Printeers Print & Ship <= 1.17.0 访问控制漏洞 — Printeers Print & Ship 6.5 Medium2026-06-02
CVE-2026-9234 JTL-Connector for WooCommerce <=2.4.1 认证设置修改缺少授权漏洞 — JTL-Connector for WooCommerce 4.3 Medium2026-06-02
CVE-2026-9050 Slider Revolution 6.0.0-6.7.55 及 7.0.0-7.0.14 任意插件停用漏洞 — Slider Revolution 4.3 Medium2026-06-01
CVE-2026-45285 Nextcloud 团队外部成员共享时隐藏公开链接创建漏洞 — security-advisories 6.4 Medium2026-06-01
CVE-2026-42671 WordPress GeoDirectory 插件 <= 2.8.157 访问控制漏洞 — GeoDirectory 6.5 Medium2026-06-01
CVE-2026-42675 WordPress Hydra Booking <=1.1.41 访问控制漏洞 — Hydra Booking 7.3 High2026-06-01
CVE-2026-42677 WordPress WP Document Revisions <=3.8.1 访问控制缺陷 — WP Document Revisions 7.5 High2026-06-01
CVE-2026-42682 WordPress wpForo论坛插件3.0.6之前版本访问控制漏洞 — wpForo Forum 9.1 Critical2026-06-01
CVE-2026-40543 SOPlanning 缺失授权验证漏洞 — SOPlanning--2026-06-01
CVE-2026-41014 Apache Airflow 分区DAG运行端点RBAC绕过漏洞 — Apache Airflow--2026-06-01
CVE-2026-8382 WordPress plugin Advanced Custom Fields 安全漏洞 — Advanced Custom Fields (ACF®) 5.3 Medium2026-05-31
CVE-2026-48811 FreeScout 安全漏洞 — freescout 4.3 Medium2026-05-29
CVE-2026-49385 JetBrains YouTrack 安全漏洞 — YouTrack 6.5 Medium2026-05-29
CVE-2026-49378 JetBrains TeamCity 安全漏洞 — TeamCity 4.3 Medium2026-05-29
CVE-2026-49374 JetBrains TeamCity 安全漏洞 — TeamCity 7.6 High2026-05-29
CVE-2026-49367 JetBrains IntelliJ IDEA 安全漏洞 — IntelliJ IDEA 8.0 High2026-05-29
CVE-2026-47742 shopper 安全漏洞 — shopper 6.5 Medium2026-05-29
CVE-2026-47745 shopper 安全漏洞 — shopper 6.5 Medium2026-05-29

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