# CVE-2023-47033: Business logic in n/a

> Attackers can exploit a reentrancy flaw in the executeTransaction function to manipulate funds in the MultiSigWallet smart contract.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2024
- **Updated:** 30 May 2025
- **Also known as:** GHSA-7qfc-6cw5-2ppm

## What is CVE-2023-47033?

CVE-2023-47033 is a high-severity vulnerability in n/a, published on 19 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MultiSigWallet 0xF0C99 was discovered to contain a reentrancy vulnerability via the function executeTransaction.

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

It affects 1 product.


Products: Multisigwallet Project Multisigwallet.

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

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

## Is CVE-2023-47033 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47033 is a high-severity vulnerability in n/a, published on 19 Jan 2024. 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-47033 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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