←
inzo216 posts
inzo avatar

inzo

@inzo____

always hunting for the unseen;

◷ Joined November 2022▧ 38 Photos and videos
inzo avatar
inzo@inzo____·22 Mar 2025

Happy to share my first article with @zhero___, which is also my first CVE (CVE-2025-29927) on the largest JS framework: Next.js. A critical vulnerability that impacts a wide range of sensitive sectors across the internet.

zhero;@zhero___22 Mar 2025

the research paper is out: Next.js and the corrupt middleware: the authorizing artifact result of a collaboration with @inzo____ that led to CVE-2025-29927 (9.1-critical) zhero-web-sec.github.io/rese… enjoy the read!

Post attachment
zhero; avatar
⟳ inzo retweeted
zhero;@zhero___·Jul 3

Pleased to publish a browser-related research paper (w/@inzo____) titled: One trigram at a time: XSLeak via Universal CSS Injection and DoS in Opera (GX) The title speaks for itself. Enjoy the read! zhero-web-sec.github.io/rese…

Post attachment
zhero; avatar
⟳ inzo retweeted
zhero;@zhero___·Jun 28

Paper currently being written. Expected to be the next publication, God willing. As no companies have yet been found whose vision and values truly align with ours, sponsorships, partnerships, and selective intellectual property transfers related to ongoing and future research remain open for discussion.

can merely visiting a website lead to cross-site data exfiltration from any site without user interaction? a ""minimal"" PoC has been validated, successfully exfiltrating, as a demonstration, the victim’s gmail address report submitted, hoping to provide more details soon

Post attachment
zhero; avatar
⟳ inzo retweeted
zhero;@zhero___·Jun 3

New short article on a real-world exploitation case rather than pure research, demonstrating how a specific mistake in Next.js can lead to a systematic zero-click SXSS on its latest versions (w/@inzo____): Re:CACHE - Excessive reflection, type confusion, and 0-click SXSS on Next.js zhero-web-sec.github.io/rese…

Post attachment
zhero; avatar
⟳ inzo retweeted
zhero;@zhero___·May 18

Now open to sponsorships, partnerships, and selective intellectual property transfers related to ongoing and future research. Current model: fully independent vulnerability research funded through bug bounty activity, with no consulting or commercial services. Interested parties can reach out via DM or via the email listed on the blog.

zhero;@zhero___21 Nov 2025

I’ve received several similar offers over the past few months from companies of various sizes involving conducting research + writing of the related papers, which generally included: - transferring research intellectual property - per-research payment, sometimes with a fixed fee

zhero; avatar
⟳ inzo retweeted
zhero;@zhero___·Jan 16

Happy to publish our first research of the year on the SvelteKit framework, downloaded over 800,000 times per week, which led to CVE-2025-67647 (w/@inzo____): Avoiding the paradox: A native full-read SSRF and one‑shot DoS in SvelteKit zhero-web-sec.github.io/rese… Enjoy the read

Post attachment
inzo avatar
inzo@inzo____·Jan 6

No doubt I’ll be voting for these two amazing pieces of research

honored to see two of my research works selected for the initial nominations they’ve been the most fruitful for me in practice, with ongoing discoveries of vuln assets, incl. several major platforms, and six figures in rewards If they helped you in any way, consider voting-14/01

Post attachment
inzo avatar
inzo@inzo____·31 Dec 2025

It was an excellent year of collaboration with my brother, during which I learned many things and we achieved a lot of results. Find out what next year will bring.

zhero;@zhero___31 Dec 2025

grateful;

Post attachment
zhero; avatar
⟳ inzo retweeted
zhero;@zhero___·19 Dec 2025

We unfortunately won’t be able to publish our latest paper before the end of 2025 as the maintainers chose to delay it until early January. Still, it’s been a productive year of zero-day discoveries, with a focus on frameworks, many of which were shared on the blog. 2025 Recap:

Post attachment
zhero; avatar
⟳ inzo retweeted
zhero;@zhero___·19 Nov 2025

second research on Astro, a shorter paper than usual, which led to CVE-2025-64764 (w/ @inzo____): Unlocking Reflected XSS in the Astro framework zhero-web-sec.github.io/rese… all applications using the Server Island feature are vulnerable

Post attachment
zhero;@zhero___13 Nov 2025

release of our new paper (w/ @inzo____) which resulted in CVE-2025-64525: Astro framework and standards weaponization from path-based middleware protection bypass to potential SSRF & XSS + full bypass of CVE-2025-61925 on @astrodotbuild zhero-web-sec.github.io/rese…

Post attachment
zhero; avatar
⟳ inzo retweeted
zhero;@zhero___·1 Nov 2025

to echo my last post, your big, influential app with millions of users is surely secure against this probably the most surprising(?) vulnerability of my short career; sometimes you just need to reach out your arm (almost literally), right @inzo____?

Post attachment
inzo avatar
inzo@inzo____·7 Aug 2025

I really enjoyed reading the latest research paper by @albinowax Big kudos to everyone who contributed to this research Super inspiring portswigger.net/research/htt…

The whitepaper is live! Learn how to win the HTTP desync endgame... and why HTTP/1.1 needs to die: http1mustdie.com/