How severe is CVE-2022-3225?

CVE-2022-3225 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-3225?

CVE-2022-3225 affects the following packages: @budibase/worker (npm), @budibase/builder (npm), @budibase/bbui (npm). Ecosystems affected: npm.

How do I fix CVE-2022-3225?

Update @budibase/worker to 1.3.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3225 is resolved across your whole dependency graph.

How do I detect CVE-2022-3225 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @budibase/worker. 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.

How do I mitigate CVE-2022-3225 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2022-3225?

O3 pinpoints whether CVE-2022-3225 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2022-3225 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-3225, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-3225?

CVE-2022-3225 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2022-3225 published, and has it been updated?

CVE-2022-3225 was published on September 16, 2022 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

CVE-2022-3225

HIGH

Improper Control of Dynamically-Managed Code Resources in budibase/budibase

Also known asGHSA-x92g-49gh-63qm

Published

Sep 16, 2022

Updated

Apr 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk48th percentile+0.33%

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

3 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@budibase/workernpm

4Kdownloads / week

@budibase/buildernpm

27downloads / week

@budibase/bbuinpm

4Kdownloads / week

Description

Improper Control of Dynamically-Managed Code Resources in GitHub repository budibase/budibase prior to 1.3.20.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@budibase/worker`	all versions	1.3.20
📦npm	`@budibase/builder`	all versions	1.3.20
📦npm	`@budibase/bbui`	all versions	1.3.20

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Improper Control of Dynamically-Managed Code Resources in GitHub reposit…

huntr.devNVDSep 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @budibase/worker. 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 @budibase/worker to 1.3.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3225 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 CVE-2022-3225 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 CVE-2022-3225. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Improper Control of Dynamically-Managed Code Resources in GitHub repository budibase/budibase prior to 1.3.20.

O3 Security · Impact-Aware SCA

Is CVE-2022-3225 in your dependencies?

O3 detects CVE-2022-3225 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works