GPEN Vulnerability Scanning Practice Question
During a penetration test, a tester runs an OpenVAS scan against a web server and receives a report indicating a high-severity vulnerability with a CVE identifier. Before including it in the final report, the tester wants to verify if the vulnerability is actually exploitable. Which action should the tester take next?
⚠ Common exam trap
The trap here is assuming that a CVE match from a scanner automatically means the target is vulnerable, when in fact manual validation is needed to confirm exploitability.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Manually test the vulnerability using a proof-of-concept exploit or crafted request.
Manual testing with a proof-of-concept or crafted request is the most reliable way to verify that a reported vulnerability is exploitable. It provides concrete evidence, reduces false positives, and ensures the finding is accurate before reporting. Other actions may offer context but do not directly confirm exploitability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Manually test the vulnerability using a proof-of-concept exploit or crafted request.
Why this is correct
Manually testing with a PoC or crafted request provides direct evidence of exploitability. It confirms whether the vulnerability is real and can be triggered in the target environment, which is essential for an accurate penetration test report. This step distinguishes between theoretical findings and actual risk.
- ✗
Check the CVE details in the National Vulnerability Database (NVD).
Why it's wrong here
Consulting the NVD provides information about the vulnerability, such as affected versions and severity, but it does not confirm that the specific target is vulnerable. The scanner may have misidentified the version or the vulnerability might be mitigated. Therefore, this action alone does not verify exploitability.
- ✗
Review the scanner's plugin documentation to understand the detection logic.
Why it's wrong here
Understanding how the scanner detects the vulnerability can help assess false positives, but it does not prove the vulnerability exists on the target. The detection logic might be based on version banners that are spoofed or inaccurate. Manual verification is still required to confirm exploitability.
- ✗
Re-run the scan with a different scanner to confirm the finding.
Why it's wrong here
Using another scanner might provide corroboration, but it does not directly verify exploitability. Different scanners may have different detection methods, and a match could still be a false positive. This approach also consumes additional time and resources without conclusively proving the vulnerability can be exploited.
About these practice questions
One of 298 original GPEN practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official GIAC exam blueprint
This GPEN practice question is part of Courseiva's free GIAC 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 GPEN exam.