How gakukohinata/timeidor works
Project type and purpose
• This is a small Node.js–based security demo (TimeIDOR) illustrating a time-based IDOR vulnerability in a “shop” web app.
• It includes a static frontend served from a public directory, a monolithic backend (server.js), and an external Python exploit script (exploit.py).
File structure
• Top-level files:
• server.js – the Node HTTP server
• exploit.py – attacker’s Python exploit script
• package.json / package-lock.json + node_modules – standard Node dependencies
• public/ – static assets and HTML pages:
• index.html – shop homepage
• cart.html – shopping cart page
• victim_inbox.html – victim’s mailbox UI
• attacker_inbox.html – attacker’s mailbox UI
README for additional insights
• The server listens on port 3388 and exposes three URLs: shop, victim mailbox, attacker mailbox.
• There is no external database; state is likely held in memory or in temporary files by server.js.
• The Python script connects to the same server to exploit the vulnerability.