# CVE-2026-75018: Missing authorization in Custom Contact Forms

> Authenticated contributors can delete arbitrary posts and modify post metadata due to missing authorization checks in the Custom Contact Forms plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A: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:** 5 Sep 2026
- **Updated:** 7 Sep 2026
- **Also known as:** GHSA-f352-gm8p-p4mp

## What is CVE-2026-75018?

CVE-2026-75018 is a medium-severity missing authorization vulnerability in outlawgt Custom Contact Forms, published on 5 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Custom Contact Forms plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.16. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to permanently force-delete arbitrary posts of any post type (including pages, administrator-authored posts, and WooCommerce products) and write arbitrary ccf_field_* post meta onto any post regardless of ownership or post type. The top-level form ID is checked via edit_post/publish_posts, but the nested fields[].ID and choices[].ID paths processed by _create_and_map_fields() and _create_and_map_choices() carry no equivalent capability or post-type guard, leaving those sinks fully exposed while delete_item() and delete_submission() contain explicit post-type restriction fixes demonstrating the developer's awareness of scoping requirements.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-75018 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75018 is a medium-severity missing authorization vulnerability in outlawgt Custom Contact Forms, published on 5 Sep 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-2026-75018 in the wild and no public exploit code.

Affected product: outlawgt Custom Contact Forms. 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-75018/ (Markdown: https://insights.sbomify.com/CVE-2026-75018/index.md)
```

## Sources

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

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