The correct next step is to upload a PHP web shell with a .phtml extension and access it via the /uploads/ directory to execute commands. This works because Apache 2.4.6 with PHP 7.2 is often configured to process .phtml files as PHP, even when .php extensions are blocked by a 403 Forbidden rule. The web shell upload via .phtml bypasses the restriction by exploiting a common misconfiguration where the server only filters the primary .php extension but leaves alternative PHP handlers like .phtml, .php5, or .php7 enabled. On the Certified Ethical Hacker CEH exam, this scenario tests your understanding of file upload vulnerabilities and Apache multi-handler configurations—a frequent trap is assuming that blocking .php alone is sufficient. Remember the memory tip: “Block .php, but .phtml slips through—always check the handler list.”
CEH Introduction to Ethical Hacking Practice Question
This CEH practice question tests your understanding of introduction to ethical hacking. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
You are a penetration tester hired by a financial services company to assess the security of their external web application. The application is a customer portal hosted on a Linux server with Apache 2.4.6 and PHP 7.2. During reconnaissance, you discover that the server responds to HTTP OPTIONS requests and the Allow header includes PUT and DELETE methods. The application uses a MySQL database backend. You also find a file upload feature in the profile section that accepts JPEG images. While testing, you notice that uploading a file with a .php extension returns a '403 Forbidden' error, but uploading a file with .php5 or .phtml extension succeeds. The uploaded files are stored in /uploads/ directory. What should be your next step to escalate the attack?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Upload a PHP web shell with .phtml extension and access it via the /uploads/ directory to execute commands.
Option B is correct because the server allows file uploads with .phtml extension, which Apache processes as PHP due to its configuration. Uploading a PHP web shell with .phtml extension to the /uploads/ directory and accessing it directly allows command execution, escalating the attack. This bypasses the 403 Forbidden restriction on .php files while leveraging the existing upload functionality.
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.
✗
Use the PUT method to upload a malicious file directly to the web root.
Why it's wrong here
PUT may be disabled or restricted; the Allow header may be misleading.
✓
Upload a PHP web shell with .phtml extension and access it via the /uploads/ directory to execute commands.
Why this is correct
This leverages the upload bypass to achieve code execution.
Related concept
Read the scenario before looking for a memorised answer.
✗
Exploit the IIS WebDAV vulnerability to execute commands.
Why it's wrong here
The server is Apache, not IIS.
✗
Attempt SQL injection in the login form to extract database credentials.
Why it's wrong here
No evidence of SQL injection vulnerability yet.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume PUT method (Option A) is the primary escalation path because it is listed in the Allow header, but they overlook that the file upload feature with .phtml extension is a confirmed, working vector that directly leads to code execution.
Detailed technical explanation
How to think about this question
Apache's mod_mime and AddHandler directives can associate multiple extensions (e.g., .phtml, .php5) with PHP processing, even if .php is blocked via mod_security or .htaccess rules. The /uploads/ directory must have execute permissions or a corresponding handler to run the PHP code; if not, the shell may be served as plain text. In real-world scenarios, attackers often chain this with directory traversal or misconfigured MIME types to achieve remote code execution.
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 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.
Introduction to Ethical Hacking — This question tests Introduction to Ethical Hacking — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Upload a PHP web shell with .phtml extension and access it via the /uploads/ directory to execute commands. — Option B is correct because the server allows file uploads with .phtml extension, which Apache processes as PHP due to its configuration. Uploading a PHP web shell with .phtml extension to the /uploads/ directory and accessing it directly allows command execution, escalating the attack. This bypasses the 403 Forbidden restriction on .php files while leveraging the existing upload functionality.
What should I do if I get this CEH question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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.