CVE-2026-92403Network attack vectorHinoki check available

Unauthenticated post modification via form ID substitution

Published Sep 19, 2026 · Updated Sep 19, 2026

Incorrect authorization in Secure Custom Fields before 6.9.4 allows remote attackers to modify post titles and content through front-end forms. The front-end acf_form() save path accepts a submitted form identifier without binding it to the form metadata rendered for that visitor, so a request can select a different registered form. Exploitation requires an anonymously reachable front-end form and a target registered form bound to a post; the consequence is limited to changing that post's title and content.

CVSS severity3.7
Low
EPSS probability0.27%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Incorrect authorization in Secure Custom Fields before 6.9.4 allows remote attackers to modify post titles and content through front-end forms. The front-end acf_form() save path accepts a submitted form identifier without binding it to the form metadata rendered for that visitor, so a request can select a different registered form. Exploitation requires an anonymously reachable front-end form and a target registered form bound to a post; the consequence is limited to changing that post's title and content.

The record

CVE
CVE-2026-92403
Published
Sep 19, 2026
Updated
Sep 19, 2026
Vendor
WordPress.org
Product
Secure Custom Fields
Classifications
CWE-863, T1565.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <6.9.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

WordPress.org · Secure Custom Fieldsversion=0 <6.9.4

Published CVSS scores

3.7CISA CoordinatorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-863Incorrect Authorization
T1565.001Stored Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started