Heuristic estimate (AI scoring not configured). SecureBananaLabs/bug-bounty: Bug: user creation accepts empty payloads and client-controlled ids shows 0 engagement on ghbounties. Buildability is inferred from the description; add an AI gateway key for a tailored read.
A starter prompt for Claude Code, what you'll need, and how to reach them.
Build a minimal version of "SecureBananaLabs/bug-bounty: Bug: user creation accepts empty payloads and client-controlled ids". Read the original at https://github.com/SecureBananaLabs/bug-bounty/issues/1766 for the exact requirements, then scaffold a Next.js + Tailwind app, implement the smallest valuable slice first, and ship it. (Enable AI scoring for a tailored, detailed prompt.)
Part of the operator's house stack.
Depends on the find — enable AI scoring for specifics.
Learn it: Search getting-started ↗
Bounty (amount on the issue). ## Description The `/api/users` creation path accepts arbitrary request bodies and forwards them directly to `createUser`. The service currently builds the user object as `{ id: `usr_${Date.now()}`, ...payload }`, so a caller can submit an `id` field and override the generated server ID. Empty or malformed payloads are also accepted because the controller does not validate `req.body`. ## Impact - Clients can create users with attacker-chosen IDs. - Empty objects can become persisted-looking user records once storage is added. - Downstream admin and profile views can receive malformed user records without `name`, `email`, or a safe role. ## Expected behavior Validate user creation input, reject unknown fields such as `id`, require a valid name and email, allow only public user roles, and keep the server-generated user ID authoritative. ## Files - `apps/api/src/controllers/userController.js` - `apps/api/src/services/userService.js` Related to #743 This issue is limited only to the creator of this issue. This means that only the issue author can attempt to solve this issue. If you would like to work on it, please create another issue with the same content
Comment /attempt on the GitHub issue, then open a PR to claim the bounty.
“Enable AI scoring for a tailored outreach angle.”
Open the original ↗