{"uuid": "822ccdab-757c-4dea-9bc8-bc547b468b9d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-46982", "type": "published-proof-of-concept", "source": "https://t.me/cybersecplayground/231", "content": "\ud83d\udea8 Next.js + WAF Bypass + SXSS via Cookie Reordering \ud83d\udea8\n\n\ud83e\udde0 Attack Summary:\nYou\u2019re dealing with:\n\n\ud83d\udd0d A Next.js app\n\n\u26a0\ufe0f Two reflected cookies in pageProps\n\u26a0\ufe0f A WAF blocking your initial attempts\n\n\ud83e\uddea Observations:\n\ud83e\udde8 Single payload \u2192 403 Forbidden\n\n\ud83e\udde8 Split payload across two cookies \u2192 Still 403\n\n\ud83e\udde8 Reorder the cookie fragments \u2192 200 OK \u2705\n\n\ud83d\udc40 That\u2019s your in! Reversing the order bypasses the WAF inspection logic \ud83d\udd04\n\n\u26a0\ufe0f Now chain it with:\n\n\ud83e\uddeb CVE-2024-46982 (Elixir Stale SSR template injection)\n\ud83d\udd17 https://github.com/masch1/CVE-2024-46982\n\n\u27a1\ufe0f This allows CP (Client-side Prototype Pollution) \u2192 Stored XSS (SXSS) in Next.js apps.\n\n\ud83d\udca3 Exploit Flow:\n    \ud83d\udc8e Bypass WAF via cookie reordering\n    \ud83d\udc8e Inject CP payload using stale Elixir template vuln\n    \ud83d\udc8e Achieve SXSS across all visiting users!\n\n\ud83d\udee1 Mitigation Tips:\n    \u2705 Sanitize cookie inputs server-side\n    \u2705 Audit template engines for unsafe parsing\n    \u2705 Patch Elixir if in stack (see CVE-2024-46982)\n\n\ud83d\udd0d Keep hunting clever chains like this. WAFs aren\u2019t invincible!\n\ud83d\udce2 Follow @cybersecplayground for more wild bug chains, PoCs, and bypass tricks\n\ud83d\udc4d Like & \ud83d\udd01 Share to help others learn!\n\n#bugbounty #nextjs #xss #sxss #wafbypass #infosec #cybersecurity #cve2024_46982", "creation_timestamp": "2025-06-15T20:52:28.000000Z"}