# CVE-2026-18946: Contact Form to Any API < 3.0.7 - Unauthenticated Sensitive File Disclosure via Predictable Filename

> Unauthenticated attackers can download sensitive files submitted by other users due to predictable filenames in the Contact Form to Any API plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-qp64-vw92-jr32

## What is CVE-2026-18946?

CVE-2026-18946 is a high-severity vulnerability in Unknown Contact Form to Any API, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Contact Form to Any API WordPress plugin before 3.0.7 does not use a random filename when copying files uploaded through contact forms into a publicly accessible directory, allowing unauthenticated attackers to enumerate and download files submitted by other users.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-18946 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18946 is a high-severity vulnerability in Unknown Contact Form to Any API, published on 10 Aug 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-18946 exists.

Affected product: Unknown Contact Form to Any API. 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-18946/ (Markdown: https://insights.sbomify.com/CVE-2026-18946/index.md)
```

## Sources

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

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