dw1[verified]@dwisiswant0PoC
The tweet lists multiple CVEs and links to a GitHub repository containing proof‑of‑concept code, indicating the vulnerabilities have been demonstrated but without mention of active exploitation, patches, or detailed technical attributes.
Nicolas Krassas[verified]@DinosnPoC
The post shares a GitHub repository containing Proof‑of‑Concept code for multiple Next.js v16.2.4 vulnerabilities, with no indication of active exploitation or available patches.
Huda Al-Assaf[verified]@0x0HudaPoC
The message announces a GitHub repository of Proof‑of‑Concept code for several CVEs in Next.js v16.2.4, without indicating active exploitation, patches, or technical details.
Upwind Security MDR[verified]@UpwindMDRDisclosure
The text announces multiple newly identified Next.js CVEs, detailing their technical impacts and advising users to monitor vendor advisories for patches.
Psycho 🎭@Psycho10k_PoC
The post shares a collection of Proof‑of‑Concept codes for multiple CVEs in Next.js v16.2.4, directing readers to a GitHub repository that likely contains exploit scripts.
termireum@termireumPoC
This post shares a GitHub repository containing proof‑of‑concept code for multiple Next.js CVEs, with no indication of active attacks, patches, or remediation details.
iototsecnews@iototsecnewsPatch
The post announces that five critical CVEs in Next.js have been fixed, describing the vulnerability types and urging users to apply the available patches.
Hacking Team@HackingTeam77PoC
The post announces a GitHub repository that publishes Proof‑of‑Concept code for several CVEs affecting Next.js v16.2.4, without mentioning patches, mitigation steps, or active exploitation.