# CVE-2026-13693: Bit Form < 3.1.0 - Unauthenticated Arbitrary File Read via Path Traversal

> Unauthenticated attackers can read arbitrary server files, including configuration files, via path traversal in the Bit Form WordPress plugin.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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:** 21 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-3cgv-fv99-x54w

## What is CVE-2026-13693?

CVE-2026-13693 is a medium-severity path traversal vulnerability in Unknown Bit Form, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Bit Form  WordPress plugin before 3.1.0 does not restrict a form file-field value to a safe path before reading the file and attaching it to a notification email, allowing unauthenticated attackers to read arbitrary server files such as the WordPress configuration file.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-13693 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13693 is a medium-severity path traversal vulnerability in Unknown Bit Form, published on 21 Jul 2026. 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-2026-13693 exists.

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

## Sources

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

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