# CVE-2023-54406: Frappe before 14.59.0 Safe Execution Flag Bypass in Server Scripts

> Authenticated high-privileged users can bypass server script sandboxing to execute arbitrary code by triggering nested script executions.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-fg2g-fx2h-8fqw, GHSA-v3vh-7qx4-f582

## What is CVE-2023-54406?

CVE-2023-54406 is a medium-severity vulnerability in frappe, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Frappe before 14.59.0 and 15.x before 15.5.0 contains a sandbox flaw where the frappe.flags.in_safe_exec global flag can become False during Server Script execution when one server script triggers another. Authenticated high-privileged users can craft a Server Script that triggers other server scripts, such as by saving a document, so the remaining code runs without safe execution protections.

Weakness: CWE-372 (Incomplete Internal State Distinction)

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


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

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

## Is CVE-2023-54406 being exploited?

There is no known exploitation of CVE-2023-54406 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54406 is a medium-severity vulnerability in frappe, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54406 in the wild and no public exploit code.

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

## Sources

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

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