OSCP Report Writing: Avoiding Common Reporting Mistakes
1. Top Reporting Mistakes
Mistake Category Overview
| Category | Common Mistakes | Impact |
|---|---|---|
| Content | Vague descriptions, missing evidence, no remediation | Report fails to communicate findings |
| Technical | Inconsistent severity, wrong CVSS scores, inaccurate descriptions | Misleads stakeholders about risk |
| Professional | Plagiarism, poor formatting, grammar errors | Reduces credibility and professionalism |
| Process | Missing scope, no timestamps, incomplete findings | Report is incomplete and unusable |
2. Content Mistakes
Mistake 1: Vague Descriptions
Problem: Descriptions are too generic to be useful.
| Bad Description | Good Description |
|---|---|
| “The system is vulnerable.” | “Apache Struts 2.5.30 on webapp.example.com (10.10.10.100) is vulnerable to CVE-2024-1234, which allows remote code execution via Content-Type OGNL injection.” |
| “There is a SQL injection.” | “A UNION-based SQL injection vulnerability exists in the ‘username’ parameter of the POST request to /login on webapp.example.com, allowing extraction of all data from the MySQL 5.7 backend database.” |
| “The password is weak.” | “The administrator account on the web application uses the default password ‘admin’, which allows unauthorized access to the administrative panel.” |
| “Privilege escalation was possible.” | “Local privilege escalation from www-data to root was achieved by exploiting CVE-2019-13272, a kernel vulnerability in Linux kernel 4.15.0-20-generic.” |
How to Avoid:
- Always include the specific system, component, and vulnerability
- Include version numbers and CVE identifiers where applicable
- Describe the exact impact of the vulnerability
Mistake 2: Missing Evidence
Problem: Findings are claimed but not supported by evidence.
| Missing Evidence | Required Evidence |
|---|---|
| No screenshots | Screenshots of exploitation and results |
| No command output | Terminal output showing the exploit |
| No flag capture | Screenshots of user.txt and root.txt |
| No HTTP requests/responses | Burp Suite or curl output |
How to Avoid:
- Take screenshots at every significant step
- Copy command output to a notes file
- Save HTTP requests and responses from Burp Suite
- Always show flag capture for OSCP
Mistake 3: No Remediation
Problem: Findings are documented but no guidance on how to fix them.
| Bad (No Remediation) | Good (With Remediation) |
|---|---|
| “SQL injection found on /login endpoint.” | “SQL injection found on /login endpoint. Remediation: Implement parameterized queries using prepared statements. Example: cursor.execute(\"SELECT * FROM users WHERE username = %s\", (username,))” |
How to Avoid:
- Always include remediation for every finding
- Provide specific, actionable steps
- Include code examples where applicable
- Reference patches, updates, or configuration changes
3. Technical Mistakes
Mistake 4: Inconsistent Severity Ratings
Problem: Similar vulnerabilities are rated with different severity levels.
| Inconsistent | Consistent |
|---|---|
| SQL injection on /login rated as Critical (9.8) | SQL injection on /login rated as Critical (9.8) |
| SQL injection on /search rated as Medium (5.3) | SQL injection on /search rated as Critical (9.8) |
How to Avoid:
- Use the CVSS calculator consistently for all findings
- Apply the same methodology across all findings
- Document your scoring rationale
- Review all severity ratings before submission
Mistake 5: Wrong CVSS Scores
Problem: CVSS scores don’t match the actual vulnerability characteristics.
| Wrong Score | Correct Score |
|---|---|
| Local privilege escalation scored as AV:N (Network) | Local privilege escalation scored as AV:L (Local) |
| Authenticated XSS scored as PR:N (None) | Authenticated XSS scored as PR:L (Low) |
| Information disclosure scored as C:H (High) | Information disclosure scored as C:L (Low) |
How to Avoid:
- Use the official First.org CVSS calculator
- Double-check each metric against the vulnerability
- Review the CVSS vector string for accuracy
- Reference Chapter 6 for CVSS scoring guidance
Mistake 6: Inaccurate Technical Descriptions
Problem: Technical descriptions contain errors or inaccuracies.
| Inaccurate | Accurate |
|---|---|
| “The vulnerability is in Apache 2.4.18.” | “The vulnerability is in Apache Struts 2.5.30 running on Apache httpd 2.4.18.” |
| “SQL injection allows remote code execution.” | “SQL injection allows data extraction from the MySQL database. Remote code execution was achieved through a separate vulnerability in Apache Struts.” |
| “The kernel exploit works on all Linux systems.” | “The kernel exploit (CVE-2019-13272) works on Linux kernel 4.15.0-20-generic specifically.” |
How to Avoid:
- Verify technical details before writing
- Reference authoritative sources (CVE databases, vendor advisories)
- Be precise about versions, components, and impact
- Don’t overstate the impact of a vulnerability
4. Professional Mistakes
Mistake 7: Plagiarism
Problem: Content is copied from other sources without attribution.
| Plagiarism | Original Work |
|---|---|
| Copying exploit description from Exploit-DB | Writing your own description based on your testing |
| Copying remediation from vendor advisory | Writing your own remediation based on your analysis |
| Using AI-generated content without modification | Using AI as a reference but writing in your own words |
| Copying from a classmate’s report | Writing your own report based on your own work |
How to Avoid:
- Write everything in your own words
- Reference sources but never copy verbatim
- Use plagiarism detection tools before submission
- For OSCP: Plagiarism results in automatic exam failure
Mistake 8: Poor Formatting
Problem: The report is difficult to read or navigate.
| Poor Formatting | Good Formatting |
|---|---|
| No headings or inconsistent heading levels | Consistent heading hierarchy (H1, H2, H3) |
| No code blocks for commands | Code blocks with language specification |
| No table of contents | Auto-generated table of contents with page numbers |
| Inconsistent fonts and styles | Consistent fonts, styles, and colors |
| No page numbers | Page numbers on every page |
How to Avoid:
- Use a template with consistent formatting
- Use your word processor’s heading styles
- Use code blocks for all commands and output
- Generate an automatic table of contents
- Review the entire report for formatting consistency
Mistake 9: Grammar and Spelling Errors
Problem: The report contains grammatical errors and typos.
| Common Errors | Corrections |
|---|---|
| “Their was a vulnerability” | “There was a vulnerability” |
| “The affect of this vulnerability” | “The effect of this vulnerability” |
| “Its a critical issue” | “It’s a critical issue” |
| “The vulnerabilty was exploited” | “The vulnerability was exploited” |
How to Avoid:
- Use a spell checker before submission
- Read the report aloud to catch errors
- Have a peer review the report
- Use Grammarly or similar tools
5. Process Mistakes
Mistake 10: Missing Scope Definition
Problem: The report doesn’t clearly define what was tested.
| Missing Scope | Clear Scope |
|---|---|
| No scope section | “The following systems were included in scope: 10.10.10.100, 10.10.10.101, 10.10.10.102” |
| No out-of-scope definition | “The following systems were explicitly out of scope: production database servers, external-facing web applications” |
How to Avoid:
- Always include a scope section in the engagement overview
- List all systems in scope
- List all systems out of scope
- Reference the rules of engagement
Mistake 11: No Timestamps
Problem: The report doesn’t include dates and times for activities.
| Missing Timestamps | With Timestamps |
|---|---|
| “I exploited the vulnerability.” | “On 2026-08-15 at 14:30 UTC, I exploited the vulnerability.” |
| No engagement timeline | “The engagement occurred from 2026-08-01 to 2026-08-05.” |
How to Avoid:
- Include dates and times for all significant activities
- Include an engagement timeline
- Record timestamps during the engagement
Mistake 12: Incomplete Findings
Problem: Findings are missing required elements.
| Incomplete Finding | Complete Finding |
|---|---|
| Finding with no severity rating | Finding with severity, CVSS score, summary, technical details, PoC, evidence, impact, remediation, references |
| Finding with no evidence | Finding with screenshots and command output |
| Finding with no remediation | Finding with specific remediation steps |
How to Avoid:
- Use a finding template for every finding
- Check that each finding has all required elements
- Review all findings before submission
6. Severity Rating Mistakes
Common Severity Errors
| Mistake | Correct Approach |
|---|---|
| Rating all findings as “High” | Use CVSS to determine accurate severity |
| Ignoring context | Consider the specific environment and impact |
| Using outdated CVSS versions | Use CVSS v3.1 or later |
| Not justifying scores | Explain why a score was chosen |
| Inconsistent scoring | Use the same methodology for all findings |
7. Evidence Collection Mistakes
Common Evidence Errors
| Mistake | Correct Approach |
|---|---|
| Screenshots without context | Include surrounding information and command prompt |
| Missing timestamps | Ensure system clock is accurate |
| Unannotated screenshots | Highlight key areas with arrows or boxes |
| Incomplete HTTP captures | Show full request and response |
| No file hashes | Hash all evidence files |
8. Remediation Mistakes
Common Remediation Errors
| Mistake | Correct Approach |
|---|---|
| “Apply patches” | “Apply Ubuntu security update USN-6543-1 by running: sudo apt update && sudo apt upgrade” |
| “Fix the vulnerability” | “Implement parameterized queries using prepared statements” |
| No prioritization | Order remediation by urgency and effort |
| No verification | Include steps to verify the fix works |
| Ignoring root cause | Address the underlying issue, not just the symptom |
9. Pre-Submission Checklist
Complete Checklist
CONTENT CHECKLIST
□ Executive summary is clear and concise (2-4 pages)
□ All findings are documented with consistent IDs
□ Each finding has:
□ Severity rating and CVSS score
□ Summary (2-3 sentences)
□ Technical details
□ Proof of Concept with steps
□ Evidence (screenshots)
□ Impact (technical and business)
□ Remediation (specific and actionable)
□ References (CVEs, CWEs, OWASP)
□ Screenshots are annotated and properly named
□ All commands are included with output
□ Remediation recommendations are specific and actionable
□ References to CVEs, CWEs, and OWASP are included
TECHNICAL CHECKLIST
□ CVSS scores are accurate and consistent
□ Severity ratings match the vulnerability characteristics
□ Technical descriptions are accurate and precise
□ Version numbers and CVE identifiers are correct
□ Impact descriptions are realistic and justified
PROFESSIONAL CHECKLIST
□ Report is free of spelling and grammar errors
□ Report follows the required template format
□ Table of contents is accurate and up to date
□ Document control table is complete
□ Report is properly formatted (headings, code blocks, tables)
□ Page numbers are correct
□ Classification marking is present
PROCESS CHECKLIST
□ Scope is clearly defined
□ Timestamps are included for all activities
□ All findings are complete (no missing elements)
□ Appendices are organized and referenced
□ Report is saved in the correct format (PDF or Word)
□ Report is named correctly
□ All work is original (no plagiarism)
□ Report has been proofread at least twice
10. Key Takeaways
- Be specific. Vague descriptions are the most common content mistake.
- Include evidence. Every finding must be supported by screenshots and output.
- Provide remediation. Every finding must have actionable fix guidance.
- Be consistent. Use the same methodology for severity ratings and formatting.
- Be accurate. Verify technical details before writing.
- Be original. Write in your own words. Plagiarism is unacceptable.
- Be professional. Proofread for grammar, spelling, and formatting.
- Use a checklist. Ensure all required elements are included before submission.
- For OSCP: Plagiarism, missing evidence, and incomplete findings are the most common reasons for report failure.
11. Further Reading
- SANS Penetration Testing Report Best Practices
- OWASP Reporting Guidelines
- NIST SP 800-115 Quality Assurance Section