WordPress security changelog
MEDIUM CVE-2025-63058 Deferred

Custom Field Template: A security weakness

Custom Field Template is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 4.3 CVSS 3.1 · audit@patchstack.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Custom Field Template
Plugin slug
custom-field-template
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Dec 09, 2025
Weakness
CWE-497 — Exposure of Sensitive System Information to an Unauthorized Control Sphere

This CVE was published Dec 09, 2025 and is one of 13 known issues for this plugin.

Update, patch or deactivate.

Update Custom Field Template to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Hiroaki Miyashita Custom Field Template custom-field-template allows Retrieve Embedded Sensitive Data.This issue affects Custom Field Template: from n/a through <= 2.7.6.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary and upstream sources