{"uuid": "7f74e63b-1be1-48f1-be54-d605b52e5b3b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-0282", "type": "seen", "source": "https://t.me/hacking_Attack/175492", "content": "CVE PoC Search\nhttps://www.reddit.com/r/redteamsec/comments/1pdxf8z/cve_poc_search/\n\nRolling out a small research utility I have been building. It provides a simple way to look up proof-of-concept exploit links associated with a given CVE. It is not a vulnerability database. It is a discovery surface that points directly to the underlying code. Anyone can test it, inspect it, or fold it into their own workflow.  A small rate limit is in place to stop automated scraping. The limit is visible at: https://labs.jamessawyer.co.uk/cves/api/whoami An API layer sits behind it. A CVE query looks like: curl -i \"https://labs.jamessawyer.co.uk/cves/api/cves?q=CVE-2025-0282\" The Web Ui is https://labs.jamessawyer.co.uk/cves/    submitted by    /u/JS-Labs  (https://www.reddit.com/user/JS-Labs) \n [link] (https://labs.jamessawyer.co.uk/cves/)   [comments] (https://www.reddit.com/r/redteamsec/comments/1pdxf8z/cve_poc_search/)", "creation_timestamp": "2026-09-02T01:00:33.533061Z"}