CEH Web Application and Injection Attacks Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  SQL Injection

  Why it's wrong here

  This option is incorrect because SQL Injection specifically targets the database layer by injecting malicious SQL commands into input fields to manipulate or extract data from the backend database. The scenario describes manipulating a user_id parameter in a URL to access another user's profile, which is an authorization bypass at the application logic level, not an attempt to directly exploit or alter database queries or structures. There is no indication of SQL syntax being used or database errors being triggered.

• ✗

  Cross-Site Scripting (XSS)

  Why it's wrong here

  This option is incorrect as Cross-Site Scripting (XSS) involves injecting malicious client-side scripts, typically JavaScript, into web pages to be executed in the victim's browser. XSS attacks aim to steal session cookies, deface websites, or redirect users, by exploiting vulnerabilities in how user-supplied data is rendered. The described action of altering a user_id parameter to view another user's profile is an authorization flaw, not a client-side script injection attack.

• ✓

  Insecure Direct Object Reference (IDOR)

  Why this is correct

  This option is correct because Insecure Direct Object Reference (IDOR) vulnerabilities occur when an application exposes a direct reference to an internal object, such as a user_id parameter, and fails to implement proper authorization checks. By simply changing the value of the user_id parameter in the request, the attacker can directly access another user's profile without explicit authorization, exploiting the application's trust in the provided identifier without verifying the user's permissions for that specific resource. This directly matches the scenario.

• ✗

  Cross-Site Request Forgery (CSRF)

  Why it's wrong here

  This option is incorrect because Cross-Site Request Forgery (CSRF) involves tricking an authenticated user into unknowingly submitting a malicious request to a vulnerable web application. An attacker crafts a forged request and embeds it into a seemingly benign page, which, when visited by the victim, causes their browser to send the unauthorized request using their active session. The scenario describes the attacker directly manipulating a parameter in their own request, not coercing another user to perform an action.

Go deeper

Related to this question