--- title: "VCODER (@vc0d3r) | Hashnode" description: "Full Stack Web Dev & Bug hunter. Read the latest articles by VCODER on Hashnode." url: "https://hashnode.com/@vc0d3r" --- @vc0d3r # VCODER @vc0d3r 路 Joined October 2023 Full Stack Web Dev & Bug hunter [Website](https://vipsecurity.zone/) ## Comments [Nice writeup and excellent work 馃憦馃敟](https://hashnode.com/posts/not-so-dirty-dancing-in-gis-sdk/6935b9294a0453e1cf983805/comment/6935bf119f6c54d920700211) Comment 路 Article 路 Dec 7, 2025 路 [DOM XSS to Account Takeover: Not-So-Dirty Dancing in GIS聽SDK](https://hashnode.com/posts/not-so-dirty-dancing-in-gis-sdk/6935b9294a0453e1cf983805) [nice writeup , thanks for sharing I have a question : so if the next\_check() checks (verify) the cname record every time (when function called) and if it matches "hashnode.network" it will prevent this attack ? and the cause of this vulnerability is because hashnode only verifies the cname record once , only when it is adding to the db, , am I correct?馃](https://hashnode.com/posts/account-takeover-due-to-dns-rebinding/66e98ac1e42f1a7e03167b3b/comment/66e995e471770e9a54e291d4) Comment 路 Article 路 Sep 17, 2024 路 [Account Takeover due to DNS Rebinding](https://hashnode.com/posts/account-takeover-due-to-dns-rebinding/66e98ac1e42f1a7e03167b3b) [nice catch !](https://hashnode.com/posts/cache-poisoning-leads-to-stored-xss-manipulation-of-response-via-accept-header/66e1d4b6821d8f7ceb764b90/comment/66e76fb27b40d2b875a295aa) Comment 路 Article 路 Sep 15, 2024 路 [Cache Poisoning Leads to Stored XSS: Manipulation of Response via Accept Header](https://hashnode.com/posts/cache-poisoning-leads-to-stored-xss-manipulation-of-response-via-accept-header/66e1d4b6821d8f7ceb764b90)