CVE-2026-92403

Secure Custom Fields < 6.9.4 - Unauthenticated Post Modification via Front-End Form ID Substitution

Published Sep 19, 2026 CVSS 3.1 · 3.7 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Secure Custom Fields WordPress plugin before version 6.9.4 allows the front‑end form submission to be accepted without confirming that the form ID matches the originally rendered form. Because this verification step is omitted, an unauthenticated user can replace the form ID in the request payload with the ID of any other registered form and directly change the title and content of the post that the targeted form is bound to. This flaw can lead to defacement, content tampering, or the insertion of malicious text that compromises the integrity of the website.

Affected Systems

WordPress sites that have installed the Secure Custom Fields plugin and are running any version earlier than 6.9.4. Any instance where the front‑end form feature is enabled is potentially vulnerable.

Risk and Exploitability

An attacker can exploit this issue by sending a crafted form submission from an unauthenticated client, as no authentication is required to reach the vulnerable endpoint. The CVSS base score of 3.7 reflects a low to moderate severity, and the EPSS score of less than 1% indicates that the probability of exploitation observed in the field is very low. The vulnerability is not listed in CISA’s KEV catalog.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Secure Custom Fields to version 6.9.4 or later
  • Implement server‑side validation to ensure that the submitted form ID matches the form displayed to the visitor and that only authorized users can modify post content
  • If an upgrade is not immediately possible, disable front‑end form submissions or require user authentication before allowing form submissions

Generated by OpenCVE AI on September 20, 2026 at 00:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions secure Custom Fields
Vendors & Products Wordpress-extensions
Wordpress-extensions secure Custom Fields
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-284
CWE-639
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'}

Type Values Removed Values Added
Weaknesses CWE-284
CWE-639
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
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Sep 19, 2026, 1:17 PM
Reserved
Sep 16, 2026, 8:52 AM
Status
Deferred
Published
Sep 19, 2026, 7:16 AM
Modified
Sep 21, 2026, 1:34 PM