Custom Field Template <= 2.7.8 - Authenticated (Contributor+) SQL Injection
medium
The Custom Field Template plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 2.7.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level acces...
- CVSS:
- 6.5
- Affected:
- up to 2.7.8
- Fixed in:
- 2.8
- Disclosed:
- Jun 29, 2026
CVE-2026-57687 on NVD →
Custom Field Template [custom-field-template] <= 2.7.5 (unfixed)
unknown
[en] Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Hiroaki Miyashita Custom Field Template allows Stored XSS.This issue affects Custom Field Template: from n/a through 2.7.5.
- Affected:
- up to 2.7.5
- Fix:
- No patched version reported
- Disclosed:
- Dec 29, 2025
CVE-2025-68607 on NVD →
Custom Field Template <= 2.7.7 - Authenticated (Contributor+) Stored Cross-Site Scripting
medium
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.7.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in...
- CVSS:
- 6.4
- Affected:
- up to 2.7.7
- Fixed in:
- 2.7.8
- Disclosed:
- Dec 24, 2025
CVE-2025-68607 on NVD →
Custom Field Template [custom-field-template] <= 2.7.4 (unfixed)
unknown
[en] 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.4.
- Affected:
- up to 2.7.4
- Fix:
- No patched version reported
- Disclosed:
- Dec 9, 2025
CVE-2025-63058 on NVD →
Custom Field Template <= 2.7.6 - Authenticated (Subscriber+) Information Exposure
medium
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.
- CVSS:
- 4.3
- Affected:
- up to 2.7.6
- Fixed in:
- 2.7.7
- Disclosed:
- Dec 8, 2025
CVE-2025-63058 on NVD →
Custom Field Template [custom-field-template] < 2.6.6
unknown
[en] Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Hiroaki Miyashita Custom Field Template allows Stored XSS.This issue affects Custom Field Template: from n/a through 2.6.5.
- Affected:
- up to 2.6.6
- Fixed in:
- 2.6.6
- Disclosed:
- Sep 15, 2024
CVE-2024-44062 on NVD →
Custom Field Template <= 2.6.5 - Authenticated (Contributor+) Stored Cross-Site Scripting
medium
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.6.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts...
- CVSS:
- 6.4
- Affected:
- up to 2.6.5
- Fixed in:
- 2.6.6
- Disclosed:
- Aug 29, 2024
CVE-2024-44062 on NVD →
Custom Field Template [custom-field-template] < 2.6.2
unknown
[en] The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's custom field name column in all versions up to, and including, 2.6.1 due to insufficient input sanitization and output escaping on user supplied custom fields. This makes it possible for authenticated attac...
- Affected:
- up to 2.6.2
- Fixed in:
- 2.6.2
- Disclosed:
- Jun 11, 2024
CVE-2024-0627 on NVD →
Custom Field Template [custom-field-template] < 2.6.2
unknown
[en] The Custom Field Template plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.6.1 via the 'cft' shortcode. This makes it possible for authenticated attackers with contributor access and above, to extract sensitive data including arbitrary post metadata.
- Affected:
- up to 2.6.2
- Fixed in:
- 2.6.2
- Disclosed:
- Jun 11, 2024
CVE-2023-6748 on NVD →
Custom Field Template [custom-field-template] < 2.6.2
unknown
[en] The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above,...
- Affected:
- up to 2.6.2
- Fixed in:
- 2.6.2
- Disclosed:
- Jun 11, 2024
CVE-2024-0653 on NVD →
Custom Field Template [custom-field-template] < 2.6.2
unknown
[en] The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'cpt' shortcode in all versions up to, and including, 2.6.1 due to insufficient input sanitization and output escaping on user supplied post meta. This makes it possible for authenticated attackers with con...
- Affected:
- up to 2.6.2
- Fixed in:
- 2.6.2
- Disclosed:
- Jun 11, 2024
CVE-2023-6745 on NVD →
Custom Field Template <= 2.6.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via shortcode
medium
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'cpt' shortcode in all versions up to, and including, 2.6.1 due to insufficient input sanitization and output escaping on user supplied post meta. This makes it possible for authenticated attackers with contribu...
- CVSS:
- 6.4
- Affected:
- up to 2.6.1
- Fixed in:
- 2.6.2
- Disclosed:
- Jun 10, 2024
CVE-2023-6745 on NVD →
Custom Field Template <= 2.6.1 - Authenticated(Constibutor+) Stored Cross-Site Scripting via Custom Field Name
medium
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's custom field name column in all versions up to, and including, 2.6.1 due to insufficient input sanitization and output escaping on user supplied custom fields. This makes it possible for authenticated attackers...
- CVSS:
- 6.4
- Affected:
- up to 2.6.1
- Fixed in:
- 2.6.2
- Disclosed:
- Jun 10, 2024
CVE-2024-0627 on NVD →
Custom Field Template <= 2.6.1 - Authenticated (Admin+) Stored Cross-Site Scritping
medium
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to in...
- CVSS:
- 4.4
- Affected:
- up to 2.6.1
- Fixed in:
- 2.6.2
- Disclosed:
- Jun 10, 2024
CVE-2024-0653 on NVD →
Custom Field Template <= 2.6.1 - Authenticated(Contributor+) Information Exposure
medium
The Custom Field Template plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.6.1 via the 'cft' shortcode. This makes it possible for authenticated attackers with contributor access and above, to extract sensitive data including arbitrary post metadata.
- CVSS:
- 4.3
- Affected:
- up to 2.6.1
- Fixed in:
- 2.6.2
- Disclosed:
- Jun 10, 2024
CVE-2023-6748 on NVD →
Custom Field Template [custom-field-template] < 2.6.1
unknown
[en] Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Hiroaki Miyashita Custom Field Template allows Stored XSS.This issue affects Custom Field Template: from n/a through 2.6.
- Affected:
- up to 2.6.1
- Fixed in:
- 2.6.1
- Disclosed:
- Mar 15, 2024
CVE-2024-25919 on NVD →
Custom Field Template <= 2.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via $search_label
medium
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the $search_label parameter in versions up to, and including, 2.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to in...
- CVSS:
- 6.4
- Affected:
- up to 2.6
- Fixed in:
- 2.6.1
- Disclosed:
- Feb 14, 2024
CVE-2024-25919 on NVD →
Custom Field Template [custom-field-template] < 2.6.0
unknown
[en] Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Hiroaki Miyashita Custom Field Template plugin <= 2.5.9 versions.
- Affected:
- up to 2.6.0
- Fixed in:
- 2.6.0
- Disclosed:
- Aug 7, 2023
CVE-2023-38392 on NVD →
Custom Field Template <= 2.5.9 - Reflected Cross-Site Scripting
medium
The Custom Field Template plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 2.5.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can succes...
- CVSS:
- 6.1
- Affected:
- up to 2.5.9
- Fixed in:
- 2.6.0
- Disclosed:
- Jul 24, 2023
CVE-2023-38392 on NVD →
Custom Field Template [custom-field-template] < 2.5.9
unknown
[en] Cross-Site Request Forgery (CSRF) vulnerability in Hiroaki Miyashita Custom Field Template plugin <= 2.5.8 versions.
- Affected:
- up to 2.5.9
- Fixed in:
- 2.5.9
- Disclosed:
- Jul 10, 2023
CVE-2023-22695 on NVD →
Custom Field Template [custom-field-template] < 2.5.2
unknown
[en] The Custom Field Template plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.5.1. This is due to missing or incorrect nonce validation on the edit_meta_value() function. This makes it possible for unauthenticated attackers to edit meta field values via a forged req...
- Affected:
- up to 2.5.2
- Fixed in:
- 2.5.2
- Disclosed:
- Jul 1, 2023
CVE-2020-36742 on NVD →
Custom Field Template [custom-field-template] < 2.5.2
unknown
- Affected:
- up to 2.5.2
- Fixed in:
- 2.5.2
- Disclosed:
- Jun 7, 2023
CVE-2021-4342 on NVD →
Custom Field Template <= 2.5.8 - Cross-Site Request Forgery via Plugin Options Update
medium
The Custom Field Template plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.5.8. This is due to missing or incorrect nonce validation on the 'custom_field_template_admin' function. This makes it possible for unauthenticated attackers to make updates to any custom field...
- CVSS:
- 4.3
- Affected:
- up to 2.5.8
- Fixed in:
- 2.5.9
- Disclosed:
- Mar 21, 2023
CVE-2023-22695 on NVD →
Custom Field Template [custom-field-template] < 2.5.8
unknown
[en] The Custom Field Template WordPress plugin before 2.5.8 unserialises the content of an imported file, which could lead to PHP object injections issues when a high privilege user import (intentionally or not) a malicious Customizer Styling file and a suitable gadget chain is present on the blog.
- Affected:
- up to 2.5.8
- Fixed in:
- 2.5.8
- Disclosed:
- Jan 2, 2023
CVE-2022-4324 on NVD →
Custom Field Template <= 2.5.7 - Authenticated (Administrator+) PHP Object Injection
high
The Custom Field Template plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 2.5.7 via deserialization of untrusted input in the custom_field_template_admin function. This allows administrator-level attackers to inject a PHP Object. No POP chain is present in the vulnerable plu...
- CVSS:
- 7.2
- Affected:
- up to 2.5.7
- Fixed in:
- 2.5.8
- Disclosed:
- Dec 9, 2022
CVE-2022-4324 on NVD →
Custom Field Template <= 2.5.1 - Cross-Site Request Forgery Bypass
medium
The Custom Field Template plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.5.1. This is due to missing or incorrect nonce validation on the edit_meta_value() function. This makes it possible for unauthenticated attackers to edit meta field values via a forged request...
- CVSS:
- 4.3
- Affected:
- up to 2.5.2
- Fixed in:
- 2.5.2
- Disclosed:
- Sep 16, 2020
CVE-2020-36742 on NVD →
Custom Field Template [custom-field-template] < 2.5.2
unknown
Cross-Site Request Forgery (CSRF) vulnerability found by Jerome Bruandet (NinTechNet) in WordPress Custom Field Template plugin (versions <= 2.5.1).
- Affected:
- up to 2.5.2
- Fixed in:
- 2.5.2
- Disclosed:
- Sep 16, 2020
Custom Field Template [custom-field-template] < 2.5.2
unknown
Over 70 plugins and themes were vulnerable to Cross-Site Request Forgery due to improperly implemented nonce protection that could be bypassed.
- Affected:
- up to 2.5.2
- Fixed in:
- 2.5.2
Custom Field Template [custom-field-template] < 2.5.2
unknown
NinTechNet discovered multiple WordPress plugins and themes vulnerable to Cross-Site Request Forgery (CSRF).
The items only check the CSRF nonce if it has been provided, making them vulnerable to CSRF attacks if the nonce is removed. This is due to the confusing use of logic operators when verifying the nonces.
- Affected:
- up to 2.5.2
- Fixed in:
- 2.5.2
Protect your WordPress site
Run a free security scan to detect vulnerable plugins and themes, exposed files, and malware — no plugin install, no signup.
Scan your site free
← Back to the vulnerability database