Server-Side Request Forgery (SSRF)
| Property | |
|---|---|
| Language |  |
| Severity |  |
| CWE | CWE-918: Server-Side Request Forgery (SSRF) |
| OWASP | A10:2021 - Server-Side Request Forgery (SSRF) |
| Confidence Level | Medium |
| Impact Level | Medium |
| Likelihood Level | Medium |
Description#
The code uses file names taken directly from user input (like $_GET, $_POST, etc.) when working with file operations. This allows users to control which files are accessed or modified, making the application vulnerable if the input isn’t properly validated or sanitized.
Impact#
An attacker could use this to read, modify, or delete sensitive files on the server, or even trigger requests to internal resources (SSRF). This can lead to data leaks, unauthorized access, or compromise of the server, potentially affecting the entire application and exposing confidential information.