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.
Published: 2026-09-19
Score: 3.7 Low
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Post Modification
Action: Patch Plugin
AI Analysis

Impact

The Secure Custom Fields WordPress plugin before version 6.9.4 fails to verify that a front‑end form submission matches the form that was rendered to the visitor. This allows an unauthenticated user to replace the form ID with that of a different registered form and alter the title and content of the post bound to that form. Such unauthorized modification can lead to defacement or loss of legitimate content, compromising the integrity of the site.

Affected Systems

WordPress sites using the Secure Custom Fields plugin, versions prior to 6.9.4. Any installation that has enabled the front‑end form functionality is potentially vulnerable.

Risk and Exploitability

The vulnerability can be exploited by sending a crafted form submission from any client without authentication. No EPSS or KEV assignment is listed, but the absence of access controls combined with the ability to modify content suggests a high severity risk. Attackers could achieve arbitrary post changes by manipulating the form ID in the request payload.

Generated by OpenCVE AI on September 19, 2026 at 09:57 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Secure Custom Fields to version 6.9.4 or later.
  • Apply server‑side validation to confirm that the submitted form ID matches the rendered form and enforce that only authorized users can modify post content.
  • If an upgrade is not immediately possible, disable front‑end form submissions or restrict them to authenticated users only.

Generated by OpenCVE AI on September 19, 2026 at 09:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 19 Sep 2026 14:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-863
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}


Sat, 19 Sep 2026 10:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-284
CWE-639

Sat, 19 Sep 2026 06:30:00 +0000

Type Values Removed Values Added
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.
Title Secure Custom Fields < 6.9.4 - Unauthenticated Post Modification via Front-End Form ID Substitution
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-09-19T13:17:56.222Z

Reserved: 2026-09-16T08:52:01.638Z

Link: CVE-2026-92403

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-19T07:16:33.683

Modified: 2026-09-19T14:17:04.080

Link: CVE-2026-92403

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-19T10:00:07Z

Weaknesses
  • CWE-284

    Improper Access Control

  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-863

    Incorrect Authorization