# CVE-2023-54412: Frappe before 13.46.3 Improper Access Control for Email Templates

> Low-privileged users can modify email templates due to improper access control, potentially altering application communications.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 12 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-f939-v9q6-j3wg, GHSA-j3ww-q4wr-xvgh

## What is CVE-2023-54412?

CVE-2023-54412 is a high-severity missing authorization vulnerability in frappe, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frappe before 13.46.3 and 14.x before 14.21.1 contains an improper access control vulnerability in Email Template permissions that allows any authenticated non-guest user to create and edit any Email Template. Attackers with low-privileged accounts, including self-registered users when signup is enabled, can modify Email Templates used by the application.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2023-54412 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54412 is a high-severity missing authorization vulnerability in frappe, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54412 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-54412/ (Markdown: https://insights.sbomify.com/CVE-2023-54412/index.md)
```

## Sources

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

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