# CVE-2024-38992: frappejs was discovered to contain a prototype pollution via the function registerView

> Attackers can execute arbitrary code or cause denial of service via prototype pollution in the registerView function of the FrappeJS library.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-gc7m-596h-x57r

## What is CVE-2024-38992?

CVE-2024-38992 is a high-severity code injection vulnerability in n/a, published on 1 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

airvertco frappejs v0.0.11 was discovered to contain a prototype pollution via the function registerView. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2024-38992?

2 open source packages ship an affected version, including @airvertco/frappejs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@airvertco/frappejs` | npm | All versions | None |
| `@airvertco/frappejs` | npm | All versions | None |

## How do I fix CVE-2024-38992?

No fix has been published for CVE-2024-38992 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-38992 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38992 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38992 and fix it if it is affected.

What it is: CVE-2024-38992 is a high-severity code injection vulnerability in n/a, published on 1 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38992 exists.

Affected packages and fixed versions:
- @airvertco/frappejs (npm): affected all versions; no fix listed
- @airvertco/frappejs (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-38992/ (Markdown: https://insights.sbomify.com/CVE-2024-38992/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38992
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38992
- OSV: https://osv.dev/vulnerability/CVE-2024-38992

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-38992/
Summaries are generated and may contain mistakes; the official description above is the record.