Post

Hack The Box Season 11 private writeups

Non-spoiler tracker for my private Hack The Box Season 11 writeup repository covering Reactor, DevHub, Connected, Checkpoint, Enigma, Paperwork, MakeSense, Bedside, DarkZeroReturns and Cohort.

Hack The Box Season 11 private writeups

Overview

I maintain a private repository for my Hack The Box Season 11 writeups:

1
https://github.com/ALLAKORI/htb-season-11-writeups

The repository is intentionally private while the machines are active. It contains full exploitation notes, CVE and vulnerability mapping, commands, evidence, attack-chain summaries, remediation guidance and redacted flags.

This public post is only a safe tracker. It does not publish active-machine solutions.

Current Season 11 coverage

MachineOSDifficultyStatus
ReactorLinuxEasyPrivate writeup completed
DevHubLinuxMediumPrivate writeup completed
ConnectedLinuxEasyPrivate writeup completed
CheckpointWindowsMediumPrivate writeup completed
EnigmaLinuxEasyPrivate writeup completed
PaperworkLinuxEasyPrivate writeup completed
MakeSenseLinuxMediumPrivate writeup completed
BedsideLinuxMediumPrivate writeup completed
DarkZeroReturnsWindows / Active DirectoryHardPrivate writeup completed
CohortLinuxEasyPrivate writeup completed

Public vulnerability coverage

The private writeups now include a dedicated CVE/vulnerability section when a named vulnerability was part of the chain.

This table is intentionally non-spoiler: it lists the vulnerability names and the broad stage only, not the exploit payloads or target-specific steps.

MachineCVEs / vulnerability names coveredBroad stage
ReactorCVE-2025-55182 React2Shell / React Server Components RCE; CVE-2025-66478 Next.js RSC advisory; Node.js Inspector misconfigurationInitial access; privilege escalation
DevHubCVE-2026-23744 MCPJam Inspector Remote Code Execution; exposed Jupyter token; hardcoded OPSMCP API key and hidden admin toolInitial access; lateral movement; privilege escalation
ConnectedCVE-2025-57819 FreePBX Endpoint Manager SQL injection to RCE; Incron / DAHDI local misconfigurationInitial access; privilege escalation
CheckpointActive Directory object recovery, ACL abuse, dMSA / BadSuccessor abuse, memory forensics, Pass-the-HashActive Directory chain
EnigmaCVE-2026-38751 OpenSTAManager module-upload RCE PoC; related CVE-2025-69212 OpenSTAManager command-injection context; CVE-2026-27626 OliveTin password argument command injectionFoothold; privilege escalation
PaperworkLPD command injection; PJL path traversal and arbitrary file write; SCM_RIGHTS file descriptor leak; password reuseInitial access; user escalation; privilege escalation
MakeSenseHardcoded client-side encryption key; stored XSS; WordPress administrator account creation; PHP reverse shell; credential reuse; internal OCR-to-PHP root RCEInitial access; lateral movement; privilege escalation
BedsideCVE-2025-64512 pdfminer.six pickle deserialization RCE; internal development-server path traversal; PyTorch checkpoint deserialization through torch.load(); shared datastore permission boundary failureInitial access; container-to-host pivot; privilege escalation
DarkZeroReturnsCVE-2026-33937 Handlebars AST injection RCE; related CVE-2021-23369 Handlebars RCE context; Gitea Actions workflow trust abuse; Kerberos/AD ACL abuse; forest-trust ExtraSID and DCSync chainInitial access; lateral movement; Linux root; domain and cross-forest compromise
CohortCVE-2026-39987 Marimo pre-auth Terminal WebSocket RCE; SSRF loopback bypass through 127.1; nginx/vhost pivot to Marimo; CVE-2026-41651 PackageKit TOCTOU / Pack2TheRootInitial access; privilege escalation

Documentation standard

Each private writeup follows the same structure:

SectionPurpose
Machine informationQuick platform, OS, difficulty and attack-focus context
SummaryShort executive explanation of the compromise path
CVEs and vulnerabilities usedNamed vulnerabilities, affected products and where they fit in the chain
Exploitation stepsReproducible notes with commands and evidence
Attack-chain summaryCompact end-to-end view of the compromise
Lessons learnedWhat the lab reinforced technically
RemediationDefensive guidance mapped to the weaknesses found
FlagsRedacted user/root flag status

Why the details stay private

Hack The Box active-machine material can include live exploitation chains, credentials, target-specific paths and flags. Publishing that publicly before retirement would spoil the lab for other players.

For that reason, the full notes stay in the private repository until the machines retire and the material can be reviewed for safe publication.

Safe public takeaway

Season 11 is useful practice for chaining realistic issues across Linux services, web applications and Windows Active Directory environments. The main value of the writeups is not just the final flag, but the discipline of documenting:

  • what was observed,
  • why a pivot made sense,
  • which evidence confirmed the path,
  • and how the same weakness could be remediated defensively.
This post is licensed under CC BY 4.0 by the author.