# CVE-2026-61343: LibreBooking path traversal

> An administrator can exploit a path traversal in the email template editor to write arbitrary files and execute code.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/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:** 9 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-7793-hmg3-gh57

## What is CVE-2026-61343?

CVE-2026-61343 is a high-severity path traversal vulnerability in LibreBooking, published on 9 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

LibreBooking's email template editor save action passes the submitted template name directly into the destination file path, allowing a remote attacker with administrator credentials to write an arbitrary file outside the template directory and execute code. Fixed in 5.1.0.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-61343?


## How do I fix CVE-2026-61343?

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

## Is CVE-2026-61343 being exploited?

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

Public exploit code:

- Librebooking Admin RCE PoC CVE-2026-61343 (github_poc): https://github.com/nmagill123/CVE-2026-61343-poc-librebooking-rce

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61343 and fix it if it is affected.

What it is: CVE-2026-61343 is a high-severity path traversal vulnerability in LibreBooking, published on 9 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61343 in the wild and no public exploit code.

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

## Sources

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

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