GHSA-j3rv-w43q-f9x2
CRITICALReact Editable Json Tree vulnerable to arbitrary code execution via function parsing
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
react-editable-json-treenpmDescription
Impact
Our library allows strings to be parsed as functions and stored as a specialized component, JsonFunctionValue. To do this, Javascript's eval function was used to execute strings that begin with "function" as Javascript. This was an oversight that unfortunately allows arbitrary code to be executed if it exists as a value within the JSON structure being displayed. Given that this component may often be used to display data from arbitrary, untrusted sources, this is extremely dangerous.
One important note is that users who have defined a custom onSubmitValueParser callback prop on the JsonTree component should be unaffected. This vulnerability exists in the default onSubmitValueParser prop which calls parse.
Patches
We have decided on a two-pronged approach to patching this vulnerability:
- Create a patch update that adds a workaround which is not enabled by default to preserve backwards-compatibility
- On the next major update, we will enable this workaround by default
The workaround we have decided on is adding a prop to JsonTree called allowFunctionEvaluation. This prop will be set to true in v2.2.2, so you can upgrade without fear of losing backwards-compatibility.
We have also implemented additional security measures as we know many people may not read the details of this vulnerability, and we want to do the best we can to keep you protected. In v2.2.2, we switched from using eval to using Function to construct anonymous functions. This is better than eval for the following reasons:
- Arbitrary code should not be able to execute immediately, since the
Functionconstructor explicitly only creates anonymous functions - Functions are created without local closures, so they only have access to the global scope
This change has brought a slight potential for breaking backwards-compatibility if users for some reason were relying on side-effects of our usage of eval, but that is beyond intended behavior, so we have decided to go ahead with this change and consider it a non-breaking change.
Workarounds
As mentioned above, there are a few scenarios you must consider:
If you use:
- Version
<2.2.2, you must upgrade as soon as possible. - Version
^2.2.2, you must explicitly setJsonTree'sallowFunctionEvaluationprop tofalseto fully mitigate this vulnerability. - Version
>=3.0.0,allowFunctionEvaluationis already set tofalseby default, so no further steps are necessary.
References
None.
For more information
If you have any questions or comments about this advisory:
- Open an issue in the GitHub repo
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-editable-json-tree | all versions | 2.2.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-editable-json-tree. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update react-editable-json-tree to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3rv-w43q-f9x2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-j3rv-w43q-f9x2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-j3rv-w43q-f9x2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j3rv-w43q-f9x2 in your dependencies?
O3 detects GHSA-j3rv-w43q-f9x2 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.