WordPress plugin · Updated daily · Source: Wordfence Intelligence

Custom Field Template vulnerabilities: affected versions and fixes

Custom Field Template has 30,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Custom Field Template at a glance

  • 15 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Sep 21, 2026.
  • Ranked #965 by popularity on WordPress.org (30,000+ active installs).
  • The latest version is 2.8.1 (released Aug 11, 2026). The most recent security fix shipped in 2.8.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Custom Field Template version

Enter the Custom Field Template version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Custom Field Template”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Custom Field Template”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.8.1). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Custom Field Template vulnerabilities

  • Custom Field Template <= 2.7.8 - Authenticated (Contributor+) Insecure Direct Object Reference to Arbitrary Media File Deletion via 'file_field' Parameter

    Missing authorization · CVE-2026-12995

    Affected versions: ≤ 2.7.8

    Fixed in: 2.8

    Severity: Medium 4.3 · Disclosed Sep 21, 2026

  • Custom Field Template <= 2.7.8 - Authenticated (Contributor+) SQL Injection via 'post_ID' Parameter

    SQL injection · CVE-2026-9855

    Affected versions: ≤ 2.7.8

    Fixed in: 2.8

    Severity: Medium 6.5 · Disclosed Sep 18, 2026

  • Custom Field Template <= 2.7.8 - Authenticated (Contributor+) SQL Injection

    SQL injection · CVE-2026-57687

    Affected versions: ≤ 2.7.8

    Fixed in: 2.8

    Severity: Medium 6.5 · Disclosed Jun 29, 2026

  • Custom Field Template <= 2.7.7 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-68607

    Affected versions: ≤ 2.7.7

    Fixed in: 2.7.8

    Severity: Medium 6.4 · Disclosed Dec 24, 2025

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

    Information disclosure · CVE-2025-63058

    Affected versions: ≤ 2.7.6

    Fixed in: 2.7.7

    Severity: Medium 4.3 · Disclosed Dec 8, 2025

  • Custom Field Template <= 2.6.5 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-44062

    Affected versions: ≤ 2.6.5

    Fixed in: 2.6.6

    Severity: Medium 6.4 · Disclosed Aug 29, 2024

  • Custom Field Template <= 2.6.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via shortcode

    Cross-site scripting (XSS) · CVE-2023-6745

    Affected versions: ≤ 2.6.1

    Fixed in: 2.6.2

    Severity: Medium 6.4 · Disclosed Jun 10, 2024

  • Custom Field Template <= 2.6.1 - Authenticated(Constibutor+) Stored Cross-Site Scripting via Custom Field Name

    Cross-site scripting (XSS) · CVE-2024-0627

    Affected versions: ≤ 2.6.1

    Fixed in: 2.6.2

    Severity: Medium 6.4 · Disclosed Jun 10, 2024

  • Custom Field Template <= 2.6.1 - Authenticated (Admin+) Stored Cross-Site Scritping

    Other weakness · CVE-2024-0653

    Affected versions: ≤ 2.6.1

    Fixed in: 2.6.2

    Severity: Medium 4.4 · Disclosed Jun 10, 2024

  • Custom Field Template <= 2.6.1 - Authenticated(Contributor+) Information Exposure

    Missing authorization · CVE-2023-6748

    Affected versions: ≤ 2.6.1

    Fixed in: 2.6.2

    Severity: Medium 4.3 · Disclosed Jun 10, 2024

  • Custom Field Template <= 2.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via $search_label

    Cross-site scripting (XSS) · CVE-2024-25919

    Affected versions: ≤ 2.6

    Fixed in: 2.6.1

    Severity: Medium 6.4 · Disclosed Feb 14, 2024

  • Custom Field Template <= 2.5.9 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-38392

    Affected versions: ≤ 2.5.9

    Fixed in: 2.6.0

    Severity: Medium 6.1 · Disclosed Jul 24, 2023

  • Custom Field Template <= 2.5.8 - Cross-Site Request Forgery via Plugin Options Update

    Cross-site request forgery (CSRF) · CVE-2023-22695

    Affected versions: ≤ 2.5.8

    Fixed in: 2.5.9

    Severity: Medium 4.3 · Disclosed Mar 21, 2023

  • Custom Field Template <= 2.5.7 - Authenticated (Administrator+) PHP Object Injection

    PHP object injection · CVE-2022-4324

    Affected versions: ≤ 2.5.7

    Fixed in: 2.5.8

    Severity: High 7.2 · Disclosed Dec 9, 2022

  • Custom Field Template <= 2.5.1 - Cross-Site Request Forgery Bypass

    Cross-site request forgery (CSRF) · CVE-2020-36742

    Affected versions: < 2.5.2

    Fixed in: 2.5.2

    Severity: Medium 4.3 · Disclosed Sep 16, 2020

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Sep 21, 2026.

Most common weaknesses in Custom Field Template

Cross-site scripting (XSS)

6 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

2 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

SQL injection

2 issues

Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.

Frequently asked questions

Is Custom Field Template safe to use?

Custom Field Template is a well-known plugin with 30,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.8.1) and turn on automatic updates.

How do I find which version of Custom Field Template my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesCustom Field Template on WordPress.org