# Secure Custom Fields <= 6.9.9 - Authenticated (Administrator+) Arbitrary Function Call via Meta Box Callback Settings

- **ID:** WPSEC-2026-3671
- **Plugin:** Secure Custom Fields (`secure-custom-fields`), https://wordpress.org/plugins/secure-custom-fields/
- **Affected versions:** all versions before 6.9.10
- **Fixed in:** 6.9.10 (Update to 6.9.10 or later.)
- **Severity:** Medium 6.6 (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H)
- **Weakness:** CWE-470
- **Usage among sites WPSec scans:** plugin Low, affected versions Low (as of 2026-11-21)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/secure-custom-fields
- **Fix released:** 2026-11-20
- **Published:** 2026-11-21
- **URL:** https://wpsec.com/vuln/WPSEC-2026-3671/

## Description

The Secure Custom Fields plugin for WordPress is vulnerable to arbitrary PHP function calls via the meta box callback settings of custom post types and taxonomies in all versions up to, and including, 6.9.9. This is due to missing restrictions on who can set the register_meta_box_cb, meta_box_cb and meta_box_sanitize_cb values, which the plugin later passes to WordPress and calls. The taxonomy sanitization callback is registered as given, without the plugin's restricted calling context. This makes it possible for authenticated attackers with Administrator-level access on multisite installations who are not super admins to have arbitrary PHP functions called, which site administrators on multisite cannot normally do.

## References

- https://wpsec.com/vuln/WPSEC-2026-3671/
- https://plugins.svn.wordpress.org/secure-custom-fields/tags/6.9.10/
- https://wordpress.org/plugins/secure-custom-fields/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-3671/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.
