How lordqba/secure-upload works
Secure Upload is a backend API demonstrating file uploads in deliberately vulnerable and hardened forms. A client reaches the server, which mounts both API variants and identifies the request’s user; each variant handles upload, listing, and download requests, using MySQL metadata and local file storage. The README also describes a browser frontend, but the sampled App.tsx is an unmodified Vite/React starter rather than an upload interface, so it is not shown as part of the upload workflow. Edges reflect sampled calls or README statements; filesystem and database services are external.
Main entry points: app.ts API application · secure.ts Secure routes · vulnerable.ts Vulnerable routes · server.ts HTTP listener
Components 9
API runtime
- HTTP listener
backend/src/server.ts - API application
backend/src/app.ts - User middleware
backend/src/user.ts
Upload variants
- Secure routes
backend/src/routes/secure.ts - Vulnerable routes
backend/src/routes/vulnerable.ts
Persistence
- MySQL database
- Files schema
schema.sql - Upload filesystem
Other components
- API client
Connections 11
- API client → HTTP listener: sends requests
README.md - HTTP listener → API application: starts
backend/src/server.ts - API application → User middleware: applies
backend/src/app.ts - API application → Secure routes: mounts secure
backend/src/app.ts - API application → Vulnerable routes: mounts vulnerable
backend/src/app.ts - API application → MySQL database: checks health
backend/src/app.ts - Secure routes → MySQL database: queries metadata
backend/src/routes/secure.ts - Secure routes → Upload filesystem: writes and downloads
backend/src/routes/secure.ts - Vulnerable routes → MySQL database: queries metadata
backend/src/routes/vulnerable.ts - Vulnerable routes → Upload filesystem: stores and downloads
backend/src/routes/vulnerable.ts - Files schema → MySQL database: defines tables
README.md