CVE-2026-92403: low-severity vulnerability in Secure Custom Fields
Secure Custom Fields < 6.9.4 - Unauthenticated Post Modification via Front-End Form ID Substitution
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 3.7epss 0.3%
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Affected products
Unknown · Secure Custom Fieldspublic PoCs found — 1
cve_referencewpscan.com/vulnerability/740341ca-6419-4980-8ee9-d9e5c0f8df92/unverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — Secure Custom Fields
In the same product, most dangerous first.
CVE-2024-9529MEDIUMSecure Custom Fields < 6.3.6.3 - Admin+ Remote Code ExecutionEPSS 0.4%CVE-2026-97194LOWSecure Custom Fields < 6.9.8 - Contributor+ Unpublished Post Title and Status Disclosure via Relational FieldsEPSS 0.2%CVE-2026-97193LOWSecure Custom Fields < 6.9.8 - Contributor+ Relationship Field Update on Arbitrary Objects via IDOREPSS 0.2%CVE-2026-97192LOWSecure Custom Fields < 6.9.8 - Contributor+ Admin-Restricted Custom Field Update via Post Save PathEPSS 0.2%CVE-2026-97195LOWSecure Custom Fields < 6.9.8 - Admin+ Stored XSS via HTML Attribute Name Injection into Field DefinitionEPSS 0.1%