# CVE-2026-92403: Secure Custom Fields < 6.9.4 - Unauthenticated Post Modification via Front-End Form ID Substitution

> Unauthenticated attackers can modify post titles and content by submitting to a different registered form than the one rendered.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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:** 19 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-6w7q-74cq-4m3f

## What is CVE-2026-92403?

CVE-2026-92403 is a low-severity missing authorization vulnerability in Unknown Secure Custom Fields, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Secure Custom Fields WordPress plugin before 6.9.4 does not properly verify that a front-end form submission corresponds to the form that was rendered to the visitor, allowing unauthenticated users to submit against a different registered form and modify the title and content of the post that form is bound to.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-92403 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92403 is a low-severity missing authorization vulnerability in Unknown Secure Custom Fields, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92403 in the wild and no public exploit code.

Affected product: Unknown Secure Custom Fields. 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-92403/ (Markdown: https://insights.sbomify.com/CVE-2026-92403/index.md)
```

## Sources

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

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