CWE-650
Trusting HTTP Permission Methods on the Server Side
Extended description
The HTTP GET method and some other methods are designed to retrieve resources and not to alter the state of the application or resources on the server side. Furthermore, the HTTP specification requires that GET requests (and other requests) should not have side effects. Believing that it will be enough to prevent unintended resource alterations, an application may disallow the HTTP requests to perform DELETE, PUT and POST operations on the resource representation. However, there is nothing in the HTTP protocol itself that actually prevents the HTTP GET method from performing more than just query of the data. Developers can easily code programs that accept a HTTP GET request that do in fact create, update or delete data on the server. For instance, it is a common practice with REST based Web Services to have HTTP GET requests modifying resources on the server side. However, whenever that happens, the access control needs to be properly enforced in the application. No assumptions should be made that only HTTP DELETE, PUT, POST, and other methods have the power to alter the representation of the resource being accessed in the request.
Common consequences3
- Access ControlGain Privileges or Assume Identity
An attacker could escalate privileges.
- IntegrityModify Application Data
An attacker could modify resources.
- ConfidentialityRead Application Data
An attacker could obtain sensitive information.
Potential mitigations1
- System Configuration
Configure ACLs on the server side to ensure that proper level of access control is defined for each accessible resource representation.
Relationships1
- ChildOfCWE-436
CVEs referencing this CWE10
| CVE | Description | Severity | EPSS | Flags | Modified |
|---|---|---|---|---|---|
| CVE-2024-28787 | IBM Security Verify Access 10.0.0 through 10.0.7 and IBM Application Gateway 20.01 through 24.03 could allow a remote attacker to obtain highly sensitive private information or cause a denial of service using a specially crafted HTTP request. IBM X-Force ID: 286584. | CRITICAL10.0 | 0.82%p52 | 2025-08-14 | |
| CVE-2022-38115 | Insecure method vulnerability in which allowed HTTP methods are disclosed. E.g., OPTIONS, DELETE, TRACE, and PUT | MEDIUM5.3 | 0.65%p46 | 2025-04-24 | |
| CVE-2023-50327 | IBM PowerSC 1.3, 2.0, and 2.1 uses insecure HTTP methods which could allow a remote attacker to perform unauthorized file request modification. IBM X-Force ID: 275109. | MEDIUM5.3 | 0.49%p38 | 2024-11-21 | |
| CVE-2024-56339 | IBM WebSphere Application Server 9.0 and WebSphere Application Server Liberty 17.0.0.3 through 25.0.0.7 could allow a remote attacker to bypass security restrictions caused by a failure to honor security configuration. | HIGH7.5 | 0.37%p29 | 2025-08-14 | |
| CVE-2024-45098 | IBM Aspera Faspex 5.0.0 through 5.0.9 could allow a user to bypass intended access restrictions and conduct resource modification. | HIGH8.1 | 0.35%p27 | 2024-09-06 | |
| CVE-2024-45097 | IBM Aspera Faspex 5.0.0 through 5.0.9 could allow a user to bypass intended access restrictions and conduct resource modification. | HIGH7.1 | 0.31%p22 | 2024-09-06 | |
| CVE-2024-45282 | Fields which are in 'read only' state in Bank Statement Draft in Manage Bank Statements application, could be modified by MERGE method. The property of an OData entity representing assumably immutable method is not protected against external modifications leading to integrity violations. Confidentiality and Availability are not impacted. | MEDIUM5.3 | 0.29%p21 | 2024-11-14 | |
| CVE-2025-21120 | Dell Avamar, versions prior to 19.10 SP1 with patch 338904, contains a Trusting HTTP Permission Methods on the Server-Side vulnerability in Security. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Information exposure. | MEDIUM6.5 | 0.26%p18 | 2026-02-26 | |
| CVE-2026-42543 | IRIS is a web collaborative platform that helps incident responders share technical details during investigations. Versions prior to 2.4.28 are vulnerable to a cross-site request forgery attack, because they use the HTTP method `GET` to change state on the server. Version 2.4.28 contains a patch. | MEDIUM4.3 | 0.17%p7 | 2026-06-08 | |
| CVE-2026-44548 | ChurchCRM is an open-source church management system. Prior to 7.3.2, top-level cross-site GET navigation from an attacker-controlled page to FundRaiserDelete.php, PropertyTypeDelete.php, or NoteDelete.php causes a logged-in ChurchCRM user with the relevant role to silently delete records, including cascaded property and record-to-property assignments. This vulnerability is fixed in 7.3.2. | HIGH8.1 | 0.12%p2 | 2026-05-13 |