The correct answer is that the application passes user input to a shell command via exec() or system() functions. This is the most likely root cause because PHP command injection via exec() and system() functions occurs when unsanitized user input is directly concatenated into a shell command string, allowing an attacker to break out of the intended command and execute arbitrary OS-level instructions. On the Systems Security Certified Practitioner SSCP exam, this scenario tests your understanding of input validation failures that lead to command injection, a common vulnerability in web applications that accept user data and feed it to system-level calls. A frequent trap is confusing command injection with SQL injection or file inclusion—remember that command injection specifically targets the operating system shell, not the database or file system. To recall this, use the mnemonic “Exec and System: Shell’s the victim” to remind you that these functions are the gateway to OS command execution.
SSCP Systems and Application Security Practice Question
This SSCP practice question tests your understanding of systems and application security. 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.
During a penetration test, an attacker was able to bypass input validation and execute commands on a web server. The server runs a PHP application. Which of the following is the MOST likely root cause?
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.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The application passes user input to a shell command via exec() or system() functions.
Option C is correct because the scenario describes command execution on the web server, which is a direct consequence of OS command injection. In PHP, passing unsanitized user input to functions like exec() or system() allows an attacker to execute arbitrary shell commands, bypassing input validation. This is the most likely root cause as it directly enables command execution, unlike other vulnerabilities that lead to different impacts.
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.
✗
The application uses unsanitized input in SQL queries.
Why it's wrong here
SQL injection leads to database access, not command execution.
✗
The application reflects user input in HTTP responses without escaping.
Why it's wrong here
XSS vulnerability, but does not directly execute commands on server.
✓
The application passes user input to a shell command via exec() or system() functions.
Why this is correct
Command injection allows arbitrary command execution on the server.
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.
✗
The application uses hidden form fields to store session tokens.
Why it's wrong here
CSRF vulnerability, not command execution.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse command injection with SQL injection or XSS, but the key differentiator is the ability to execute OS-level commands on the server, which only occurs through shell execution functions like exec() or system().
Trap categories for this question
Command / output trap
SQL injection leads to database access, not command execution.
Detailed technical explanation
How to think about this question
PHP's exec() and system() functions invoke the underlying shell (e.g., /bin/sh) to run commands, and if user input is concatenated directly, an attacker can inject shell metacharacters like ;, |, or && to chain arbitrary commands. For example, input like '127.0.0.1; cat /etc/passwd' in a ping command could leak sensitive files. This vulnerability is often exploited in web applications that perform system-level operations like network diagnostics or file processing.
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.
TExam Day Tips
→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 SOC analyst notices unusual lateral movement in the network at 2 AM. The IR playbook dictates: identify and contain (isolate the affected machine), then eradicate (remove the malware), then recover (restore from backup), then document. Skipping containment before eradication risks the attacker regaining access. Questions like this test the sequence and rationale of incident response phases.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Systems and Application Security — This question tests Systems and Application Security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The application passes user input to a shell command via exec() or system() functions. — Option C is correct because the scenario describes command execution on the web server, which is a direct consequence of OS command injection. In PHP, passing unsanitized user input to functions like exec() or system() allows an attacker to execute arbitrary shell commands, bypassing input validation. This is the most likely root cause as it directly enables command execution, unlike other vulnerabilities that lead to different impacts.
What should I do if I get this SSCP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 SSCP practice question is part of Courseiva's free ISC2 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 SSCP 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.