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.

• ✗

  Blind XSS

  Why it's wrong here

  Blind XSS is a specific subtype of stored XSS where the malicious payload is saved on the server but executes in a context not directly visible to the attacker, such as an administrative backend or a logging system. The attacker typically doesn't receive an immediate visual confirmation of execution. While it involves storage, the key differentiator is the delayed and out-of-band execution, often requiring an external callback mechanism to confirm success. This differs from a general stored XSS where the script might execute for any user viewing the affected page.

• ✗

  Reflected XSS

  Why it's wrong here

  Reflected XSS involves a malicious script being embedded in a request and then immediately "reflected" back in the server's response to the user's browser without being permanently stored on the server. The payload is typically delivered via a URL parameter or form input and only executes for the user who made the specific request. This non-persistent nature means the attacker must trick each victim into clicking a specially crafted link to trigger the vulnerability.

• ✗

  DOM-based XSS

  Why it's wrong here

  DOM-based XSS occurs entirely on the client-side, where the vulnerability arises from client-side JavaScript manipulating the Document Object Model (DOM) in an unsafe manner. Unlike reflected or stored XSS, the payload might not even be sent to the server or stored there; instead, it's processed by the browser's JavaScript engine. The malicious script executes due to client-side code dynamically writing untrusted data into the DOM, often from URL fragments or local storage.

• ✓

  Stored (persistent) XSS

  Why this is correct

  Stored, or persistent, XSS is the most dangerous type, as the malicious script is permanently saved on the target server, typically in a database, comment section, or forum post. Once stored, the payload is delivered to every user who accesses the affected web page, without requiring any further interaction from the attacker. This allows for widespread and long-term compromise, as the script executes automatically each time the vulnerable content is rendered by a user's browser.

Go deeper

Related to this question