SELECT * FROM products WHERE product_id = $_GET['id']; The developer assumed that the id coming from the URL would always be a number. They did not "sanitize" the input.
By: Cybersecurity Insights Team
| Search Query | What it finds | | :--- | :--- | | inurl:index.php?id= | Standard SQLi potential | | inurl:product.php?id= | E-commerce SQLi | | inurl:index.php?catid= | Category based injection | | inurl:page.php?file= | Local File Inclusion (LFI) | | inurl:index.php?page=admin | Admin panel exposure | inurl index.php%3Fid=
As we move further into the age of APIs, JavaScript frameworks, and serverless architecture, the humble ?id= parameter fades into obscurity. But in the dark corners of the web, on forgotten servers running PHP 5.2, the query still works. SELECT * FROM products WHERE product_id = $_GET['id'];
For modern developers, seeing your site in this search result is a wake-up call. For security professionals, it is a reminder that old habits die hard. And for criminals? It is a list of potential victims. But in the dark corners of the web,
$id = $_GET['id']; $stmt = $conn->prepare("SELECT * FROM users WHERE id = ?"); $stmt->bind_param("i", $id); // The "i" forces the input to be an integer. $stmt->execute(); Alternatively, if you cannot rewrite the backend, cast the variable to an integer:
$id = $_GET['id']; $result = mysqli_query($conn, "SELECT * FROM users WHERE id = $id");
Hot Topics