# CVE-2023-30363: Prototype Pollution in vConsole

> Prototype pollution in vConsole allows attackers to inject properties into Object.prototype, potentially leading to arbitrary code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Apr 2023
- **Updated:** 3 Feb 2025
- **Also known as:** GHSA-f737-3fh6-jf6w

## What is CVE-2023-30363?

CVE-2023-30363 is a critical code injection vulnerability in n/a, published on 26 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

vConsole v3.15.0 was discovered to contain a prototype pollution due to incorrect key and value resolution in setOptions in core.ts.

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

## Which versions are affected by CVE-2023-30363?

2 open source packages ship an affected version, including vconsole. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vconsole` | npm | All versions | 3.15.1 |
| `vconsole` | npm | All versions | 3.15.1 |

Products: Tencent Vconsole.

## How do I fix CVE-2023-30363?

Upgrade vconsole to 3.15.1 or later.

## Is CVE-2023-30363 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30363 and fix it if it is affected.

What it is: CVE-2023-30363 is a critical code injection vulnerability in n/a, published on 26 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30363 exists.

Affected packages and fixed versions:
- vconsole (npm): affected all versions; fixed in 3.15.1
- vconsole (npm): affected all versions; fixed in 3.15.1

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-2023-30363/ (Markdown: https://insights.sbomify.com/CVE-2023-30363/index.md)
```

## Sources

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

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