CVE-2026-92403
LOWDescription
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.
Is your site exposed to CVE-2026-92403?
Run a free security scan — no signup, results in seconds.
CVSS v3.1 Score
EPSS — Exploit Prediction
EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.
Weakness Type (CWE)
References
Frequently Asked Questions
What is CVE-2026-92403? +
How severe is CVE-2026-92403? +
How do I check if I'm vulnerable to CVE-2026-92403? +
Related Vulnerabilities
Incorrect authorization in Navigation in Google Chrome prior to 152.0.7977.75 allowed a remote attacker who had compromised the renderer process …
Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik …
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. From version …
Payload is a free and open source headless content management system. In versions from 3.0.0 before 3.90.0 and canary versions …
A SQL injection (CWE-89) and security boundary bypass (CWE-863) vulnerability exists in the prebuilt BigQuery forecasting tool (bigquery-forecast) of googleapis/mcp-toolbox. …
In OpenStack Mistral through 23.0.0, several of the v2 API write paths resolve the target object with a query that …