HTB CWES study materials
HTB CWES study resources

HTB CWES study plan

HTB CWES · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Injection Vulnerabilities (SQLi, Command Injection, SSTI, LDAP/XPath)

  • Map every SQL injection variant (in-band UNION, error-based, boolean/time-based blind, second-order) to the exact HTTP parameter and DBMS error signature that reveals it

  • Practice manual UNION column-count discovery and data extraction against a local MySQL and PostgreSQL instance without relying on sqlmap output

  • Build a decision tree for choosing between sqlmap tamper scripts and hand-written payloads when a WAF filters quotes, spaces, or keywords

  • Demonstrate command injection via separators, substitution, and blind out-of-band channels (DNS or HTTP callback) on a deliberately vulnerable app

  • Write a one-page comparison of SSTI payload escalation across Jinja2, Twig, and Freemarker engines, noting sandbox escape primitives

Your checkpoint

A personal injection cheat sheet with at least 15 verified payloads, each annotated with the DBMS/engine, the detection signal, and the bypass it defeats, plus screenshots of successful extraction in a lab VM

Week 2

Injection Vulnerabilities (SQLi, Command Injection, SSTI, LDAP/XPath) & Web Application Reconnaissance and Enumeration

  • Enumerate LDAP and XPath injection points by identifying filter syntax in login forms and search endpoints, then craft authentication-bypass payloads for each

  • Automate content discovery with ffuf and feroxbuster using tailored wordlists, and record how response size and status codes distinguish real endpoints from soft-404s

  • Extract and analyze JavaScript bundles and source maps to uncover hidden API routes, parameters, and client-side validation logic

  • Fingerprint a target stack from headers, cookies, error pages, and default files, and document the evidence trail for each technology identified

  • Chain a recon finding into a confirmed injection vulnerability end-to-end on a lab target

Your checkpoint

A recon-to-exploit report for one lab target: technology fingerprint table, discovered endpoint inventory with evidence, and at least one confirmed injection with a reproducible request/response transcript

Week 3

Cross-Site Scripting and Client-Side Attacks (XSS, CSRF, DOM clobbering, prototype pollution)

  • Classify XSS sinks by context (HTML body, attribute, JavaScript string, URL, CSS) and write context-appropriate payloads for each

  • Bypass common filters and CSP policies using encoding tricks, DOM-based sinks, and trusted-script gadgets, documenting why each bypass works

  • Build a CSRF proof-of-concept against a state-changing endpoint and explain the token, SameSite, and Origin-header defenses that would stop it

  • Exploit DOM clobbering and client-side prototype pollution in a lab app to achieve script execution or logic bypass

  • Convert a stored XSS into session theft or an admin-action forgery in a lab, then write the mitigation for each step

Your checkpoint

A client-side attack portfolio containing four working PoCs (reflected XSS, stored XSS, CSRF, prototype pollution) with payload source, execution evidence, and a matching defense note for each

Week 4

Authentication, Session, and Access Control Flaws (JWT, OAuth, IDOR, privilege escalation)

  • Forge, crack, and abuse JWTs: test alg=none, key confusion, weak HMAC secrets, and kid/jku injection against a lab API

  • Trace an OAuth 2.0 authorization-code flow and demonstrate redirect_uri manipulation, missing state, and token leakage in referrer or logs

  • Enumerate IDOR and horizontal/vertical privilege escalation by scripting authenticated requests with two privilege levels and diffing responses

  • Test session lifecycle flaws: fixation, predictable tokens, missing rotation on login, and logout invalidation gaps

  • Document an access-control matrix mapping each role to every endpoint and flag every mismatch

Your checkpoint

An access-control matrix spreadsheet covering at least 10 endpoints across three roles, with at least three confirmed authorization flaws and their exact reproduction steps

Week 5

File Inclusion, Upload, and Path Traversal Exploitation

  • Exploit local and remote file inclusion across PHP wrappers (php://filter, data://, expect://) and log-poisoning to reach code execution

  • Bypass upload restrictions using content-type, magic-byte, extension double, and .htaccess tricks, then verify execution

  • Traverse paths with encoding variants (dot-dot-slash, URL encoding, null bytes) to read files outside the web root

  • Escalate a file-read primitive into credential discovery and then into a shell on a lab host

  • Write a wrapper-and-filter reference table for PHP, Java, and Node targets

Your checkpoint

A file-inclusion and upload lab write-up showing at least three distinct bypass techniques with the exact request used, the server response, and the resulting file access or code execution

Week 6

Server-Side Request Forgery and Deserialization Vulnerabilities

  • Exploit SSRF against cloud metadata endpoints, internal services, and localhost-only admin panels, including filter bypass via redirects and DNS rebinding

  • Distinguish blind SSRF from full-read SSRF and set up an out-of-band listener to confirm both

  • Identify deserialization sinks in Java, PHP, and Python apps and build a gadget chain using a public tool such as ysoserial or PHPGGC in a lab

  • Analyze a serialized payload byte-by-byte to explain how the gadget chain reaches command execution

  • Write the detection and remediation guidance for both SSRF and unsafe deserialization

Your checkpoint

A two-part lab report: an SSRF chain that reaches a simulated metadata service and returns credentials, and a deserialization exploit with an annotated gadget chain and a remediation section

Week 7

Web Framework and CMS-Specific Exploitation & Post-Exploitation, Pivoting, and Web Shell/Command-and-Control Tradecraft

  • Enumerate and exploit a WordPress installation: version fingerprinting, plugin/theme enumeration with wpscan, and an authenticated admin-to-RCE path

  • Identify and exploit a known framework-specific vulnerability (for example a Spring, Laravel, or Apache Struts issue) in a lab environment

  • Deploy a minimal web shell, then upgrade to an interactive reverse shell and establish persistence through a low-privilege service account

  • Pivot from a compromised web host to an internal service using proxychains or SSH tunneling and document the network path

  • Practice operational hygiene: clean up artifacts, avoid noisy commands, and log every action for the report

Your checkpoint

An end-to-end lab chain from CMS or framework exploit to internal pivot, with a network diagram, command log, and cleanup checklist

Week 8

Professional Reporting and Remediation Guidance & Web Application Reconnaissance and Enumeration

  • Write a full penetration test report for one prior lab target with executive summary, methodology, findings rated by CVSS, and reproduction steps

  • Rewrite three findings as developer-ready remediation guidance with concrete code or configuration fixes

  • Timebox a 90-minute mock assessment on an unseen lab target and produce a findings list under exam-like pressure

  • Review the whole plan's cheat sheets and access-control matrix, and close gaps flagged by self-assessment

  • Draft a personal exam-day playbook covering enumeration order, note-taking, and time allocation

Your checkpoint

A complete professional report on one lab target, including at least five findings with CVSS scores, remediation guidance, and an executive summary a non-technical reader could act on

Milestones

Week 2: Can identify and exploit SQL, command, SSTI, LDAP, and XPath injection from a black-box lab target without external hints, and explain the detection signal for each

Week 4: Can forge or crack a JWT, demonstrate an OAuth redirect_uri flaw, and produce a role-to-endpoint access-control matrix with confirmed mismatches

Week 6: Can chain SSRF to internal credential access and build a working deserialization gadget chain, explaining each step of the chain

Week 8: Can complete a timed mock assessment and deliver a scored, remediation-ready report within the time budget