The correct answer is a missing CSRF token, because while SameSite=Lax offers some protection against cross-site request forgery, it does not block state-changing POST requests initiated from top-level navigations, such as a hidden form submission from a malicious page. The SameSite=Lax attribute only prevents cookies from being sent on cross-site requests initiated by third-party scripts or images, but a top-level form POST—like the one crafted by the penetration tester—still includes the session cookie, leaving the endpoint vulnerable. On the Certified Ethical Hacker CEH exam, this scenario tests your understanding of defense-in-depth; a common trap is assuming SameSite alone is sufficient, when in fact a server-validated CSRF token is the primary mitigation for unpredictable state changes. Remember the mnemonic: “SameSite is a shield, but a token is the lock.”
CEH Web Application and Injection Attacks Practice Question
This CEH practice question tests your understanding of web application and injection attacks. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A penetration tester intercepts the following request using Burp Suite: POST /change_password HTTP/1.1 Host: example.com Cookie: sessionid=abc123; SameSite=Lax Content-Type: application/x-www-form-urlencoded new_password=Hacker123 The tester successfully crafts a CSRF attack by embedding a hidden form in a malicious page. Which mitigation is most likely missing?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Why wrong: SameSite=Strict would prevent the cookie from being sent on cross-site requests, but the attack might still work if the cookie is not required for the state change. CSRF token is the standard mitigation.
B
HTTPOnly flag
Why wrong: HTTPOnly prevents client-side script access to the cookie, not CSRF.
C
Secure flag
Why wrong: Secure flag ensures cookie is only sent over HTTPS, but does not prevent CSRF.
D
CSRF token
A CSRF token would prevent the attack because the malicious site cannot guess the token.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
CSRF token
The presence of a SameSite cookie set to Lax does not prevent CSRF for state-changing requests like password change if the attack uses a GET or POST from a top-level navigation. However, the primary missing mitigation is a CSRF token, which is a unique unpredictable value tied to the session and validated by the server.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
SameSite=Strict
Why it's wrong here
SameSite=Strict would prevent the cookie from being sent on cross-site requests, but the attack might still work if the cookie is not required for the state change. CSRF token is the standard mitigation.
✗
HTTPOnly flag
Why it's wrong here
HTTPOnly prevents client-side script access to the cookie, not CSRF.
✗
Secure flag
Why it's wrong here
Secure flag ensures cookie is only sent over HTTPS, but does not prevent CSRF.
✓
CSRF token
Why this is correct
A CSRF token would prevent the attack because the malicious site cannot guess the token.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the CEH exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CEH question in full detail.
Identify which CEH exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Web Application and Injection Attacks — This question tests Web Application and Injection Attacks — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: CSRF token — The presence of a SameSite cookie set to Lax does not prevent CSRF for state-changing requests like password change if the attack uses a GET or POST from a top-level navigation. However, the primary missing mitigation is a CSRF token, which is a unique unpredictable value tied to the session and validated by the server.
What should I do if I get this CEH question wrong?
Identify which CEH exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CEH practice question is part of Courseiva's free EC-Council certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CEH exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.