RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Juice Shop] Add a new `/api/userPreferences` endpoint for prototype pollution challenge

Propose adding a `/api/userPreferences` endpoint that allows a naive recursive merge of user-sent JSON, which could lead to prototype pollution. This would create a new challenge for users to exploit a common Node.js bug.

Original Source

@@piyush140104 | 0 pts | 2/27/2026

# :star: Challenge idea ### Description While digging into the codebase I noticed `b2bOrder.ts` uses `notevil` to eval user input and it got me thinking about prototype pollution. Right now there's no challenge around it, which feels like a gap since it's a real and common Node.js bug. The idea is simple add a `/api/userPreferences` endpoint that does a naive recursive merge of whatever JSON the user sends. No `__proto__` filtering, no `hasOwnProperty` check. A player who figures out to send `{"__proto__": {"isAdmin": true}}` poisons the whole server's prototype chain and can access something they shouldn't. ### Underlying vulnerability/ies - **CWE-1321** - Prototype Pollution - **OWASP A03:2021** - Injection - Same root cause as CVE-2019-10744 in lodash, CVE-2019-11358 in jQuery ### Expected difficulty | :heavy_check_mark: / :x: | Difficulty | |:------------------------:|:-------------------------------------| | :x: | :star:

Discussion

Loading comments...