CVE-2026-92403

Secure Custom Fields <= 6.9.3 - Missing Authorization

2026-09-17 00:00
Charles Vosburgh

Strategic Overview

Status
Patched in 6.9.4
Affected Plugin
Secure Custom Fields
Affected Version
<= 6.9.3
CVSS
5.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2026-92403
View all Secure Custom Fields vulnerabilities

At a glance

CVE-2026-92403 is a medium-severity Incorrect Authorization vulnerability in the Secure Custom Fields WordPress plugin, affecting versions <= 6.9.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.9.4; sites on affected versions should update now. Disclosed September 2026, reported by Charles Vosburgh.

Vulnerability Overview

The Secure Custom Fields plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 6.9.3. This is due to a missing capability check on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-863: Incorrect Authorization

Reaching this weakness in Secure Custom Fields <= 6.9.3 takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For Secure Custom Fields the fix is 6.9.4: builds <= 6.9.3 are affected, anything from 6.9.4 onward is not.

Remediation

Update to version 6.9.4, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Secure Custom Fields 6.9.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C