General discussion

[Lolka555]

Each function contains textual reflections from LLM.

const actionFn = await decodeAction(formData, serverManifest);
Basically, we export the functions ourselves and call them ourselves via a POST request.

This might be suitable as a training lab for understanding the server, but it's not a real exploit.

[SakshamInABox]

+1, this is not an actual PoC and is unfortunately muddying the waters for blue teamers.

https://react2shell.com/

[p1xel007]

yes, this poc is bullshit dude

[vladko312]

CVE-2025-55182 cannot be exploited unless an attacker is able to change the serverManifest.

@Arsik0153 What is the source of that information? From the oficial sources it seems like there is no requirements for anything for the CVE to be exploitable.

This PoC doesn't show the exploitation of the CVE. It shows RCE through an artificially made vulnerability in the example server, just using a vulnerable module to make it appear legit. This PoC will still be vulnerable even after the update to the safe version.

[lionkor]

This slop is now posted on the CVE website too... https://www.cve.org/CVERecord?id=CVE-2025-55182

[lionkor]

The infosec world needs less Clanker shit, not more <3

Trying to reproduce a PoC is fair. Doing it with AI is sort of pointless, but whatever. Then posting it everywhere is just not good practice.

[ejpir]

I understand, I only posted it on hackernews with the caveat that I wasn't sure and in one thread on Twitter. What do you guys want me to do?

[lionkor]

Put the fact that it's not an accurate PoC, or that its unrelated to the CVE, in the top of the readme, so people dont waste time. Thats probably easiest.

[ejpir]

check the README, is that enough?

[lionkor]

I personally think thats plenty :) thank you for being understanding

[ejpir]

check again, made it more visible. Again, my sincere apologies

[vladko312]

check again, made it more visible. Again, my sincere apologies

@ejpir What is the source of the vulnerability alone not leading to RCE?

CVSS score and the domain of https://react2shell.com/ suggest otherwise.

[ejpir]

Maybe you can put a suggestion here for the page, as I'm a little lost what to put there and you seem to know more

[vladko312]

⚠️ THIS IS NOT A REAL POC - EDUCATIONAL ONLY ⚠️

IMPORTANT: This repository is an unsuccessful attempt to understand and replicate CVE-2025-55182 using Claude. The PoC turned out to be intentionally insecure and does NOT represent exploitation of CVE-2025-55182. (see issue #1)

Why This Doesn't Work

The PoC explicitly registers dangerous modules (fs, child_process, vm) in the server manifest - something real applications never do. In real React Server Components The manifest is build-time generated - only contains legitimate Server Actions.

From the fix it seems like the real vulnerability is triggered by accessing some internal property of an object containing server actions (e.g. __proto__ or constructor), but the PoC is not public at the moment. Refer to https://react2shell.com/ for details from the original discoverer.

Bottom line: This repository contains a vulnerable server generated by AI, not the exploitation of CVE-2025-55182.

See issue #1 for discussion.

---

[ejpir]

thanks, updated

[teaim]

Can't agree more.
That's an absolutely clickbaity GitHub repo name.