---
title: "Discussion on \"What a Single File Name Taught Me About IDOR (PortSwigger Lab)\" | Hashnode"
description: "Discussion on \"What a Single File Name Taught Me About IDOR (PortSwigger Lab)\". A PortSwigger access control lab where a chat transcript downloaded as 2.txt, and that one detail was the whole vulnerability."
url: "https://hashnode.com/posts/what-a-single-file-name-taught-me-about-idor-portswigger-lab/6aae3716aba8a64317cad7e8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [What a Single File Name Taught Me About IDOR (PortSwigger Lab)](https://david-essien.hashnode.dev/what-a-single-file-name-taught-me-about-idor-portswigger-lab?utm_source=hashnode&utm_medium=feed)

A PortSwigger access control lab where a chat transcript downloaded as 2.txt, and that one detail was the whole vulnerability.

Sep 19 · 4 min read · david-essien.hashnode.dev  
Read the article

-   [#cybersecurity](https://hashnode.com/tag/cybersecurity)
-   [#web-development](https://hashnode.com/tag/web-development)
-   [#idor](https://hashnode.com/tag/idor)
-   [#portswigger](https://hashnode.com/tag/portswigger)
-   [#access-control](https://hashnode.com/tag/access-control)

## Written by

[David Essien](https://hashnode.com/@davidessien)

@davidessien · Lagos, Nigeria

  
[View profile](https://hashnode.com/@davidessien)

Software engineer writing about systems, security, and the code behind them.

I write about backend architecture and the practical decisions behind shipping production systems — authentication and security patterns in NestJS, AI model integration, and lately Solana-based fintech infrastructure. More to come. Mostly notes from things I've actually built and broken, not theory for its own sake.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
