CWE-285: Improper Authorization
1534 CVEs have CWE-285 as their primary weakness. 1 of them are in the CISA KEV catalog. The highest EPSS score among them is 99.225%.
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Child of CWE-284: Improper Access Control
Mitigations
- 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) 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 same role.
- Architecture and Design: Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply 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 to the patient and the patient's doctor.
- 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 that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- 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.
Observed examples
- CVE-2024-6845: chatbot Wordpress plugin does not perform authorization on a REST endpoint, allowing retrieval of an API key
- CVE-2022-24730: Go-based continuous deployment product does not check that a user has certain privileges to update or create an app, allowing adversaries to read sensitive repository information
- CVE-2009-3168: Web application does not restrict access to admin scripts, allowing authenticated users to reset administrative passwords.
- CVE-2009-2960: Web application does not restrict access to admin scripts, allowing authenticated users to modify passwords of other users.
- CVE-2009-3597: Web application stores database file under the web root with insufficient access control (CWE-219), allowing direct request.
- CVE-2009-2282: Terminal server does not check authorization for guest access.
- CVE-2009-3230: Database server does not use appropriate privileges for certain sensitive operations.
- CVE-2009-2213: Gateway uses default Allow configuration for its authorization settings.
- CVE-2009-0034: Chain: product does not properly interpret a configuration option for a system group, allowing users to gain privileges.
- CVE-2008-6123: Chain: SNMP product does not properly parse a configuration option for which hosts are allowed to connect, allowing unauthorized IP addresses to connect.
- CVE-2008-5027: System monitoring software allows users to bypass authorization by creating custom forms.
- CVE-2008-7109: Chain: reliance on client-side security (CWE-602) allows attackers to bypass authorization using a custom client.
- CVE-2008-3424: Chain: product does not properly handle wildcards in an authorization policy list, allowing unintended access.
- CVE-2009-3781: Content management system does not check access permissions for private files, allowing others to view those files.
- CVE-2008-4577: ACL-based protection mechanism treats negative access rights as if they are positive, allowing bypass of intended restrictions.
- CVE-2008-6548: Product does not check the ACL of a page accessed using an include directive, allowing attackers to read unauthorized files.
- CVE-2007-2925: Default ACL list for a DNS server does not set certain ACLs, allowing unauthorized DNS queries.
- CVE-2006-6679: Product relies on the X-Forwarded-For HTTP header for authorization, allowing unintended access by spoofing the header.
- CVE-2005-3623: OS kernel does not check for a certain privilege before setting ACLs for files.
- CVE-2005-2801: Chain: file-system code performs an incorrect comparison (CWE-697), preventing default ACLs from being properly applied.
- CVE-2001-1155: Chain: product does not properly check the result of a reverse DNS lookup because of operator precedence (CWE-783), allowing bypass of DNS-based access restrictions.
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2021-28799 | 2021-05-13 | CRITICAL | 10.0 | 78.250% | An improper authorization vulnerability has been reported to affect QNAP NAS running HBS 3 (Hybrid Backup Sync. ) If exploited, the vulnerability allows remote… |
| CVE-2026-121708 | 2026-11-16 | HIGH | 8.1 | not scored | OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260513.0, Draft Workspace identifiers are… |
| CVE-2026-124222 | 2026-11-16 | MEDIUM | 6.5 | not scored | Improper authorization in Microsoft Office SharePoint allows an authorized attacker to elevate privileges over a network. |
| CVE-2026-21173 | 2026-11-16 | MEDIUM | 6.0 | not scored | Improper authorization in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to initiate an unauthorized APK restoration. |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-285'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-285'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).