CVE-2025-63058

Custom Field Template <= 2.7.6 - Authenticated (Subscriber+) Information Exposure

2025-12-08 00:00

Strategic Overview

Status: Patched in 2.7.7
Affected Plugin: Custom Field Template
Affected Version: <= 2.7.6
CVSS: 4.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2025-63058

View all Custom Field Template vulnerabilities

At a glance

CVE-2025-63058 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Custom Field Template WordPress plugin, affecting versions <= 2.7.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.7.7; sites on affected versions should update now. Disclosed December 2025, reported by Phat RiO.

Vulnerability Overview

The Custom Field Template plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.7.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive user or configuration data.

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 interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Custom Field Template <= 2.7.6 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Custom Field Template the fix is 2.7.7: builds <= 2.7.6 are affected, anything from 2.7.7 onward is not.

Remediation

Update to version 2.7.7, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Custom Field Template 2.7.7 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-63058 https://www.wordfence.com/threat-intel/vulnerabilities/id/ee342bda-f2bb-45dd-ae9b-a254006b9bd2 https://nvd.nist.gov/vuln/detail/CVE-2025-63058

Related records

Other vulnerabilities in Custom Field Template

CVSS Vector

4.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/