Vulnerabilities and security researches forcustom-field-template custom-field-template
Direction: ascendingJun 06, 2024
Custom Field Template # CVE-2020-36742
- CVE, Research URL
- Home page URL
- Application
- Date
- Jul 01, 2023
- Research Description
- 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 granted they can trick a site administrator into performing an action such as clicking on a link.
- Affected versions
-
max 2.5.2.
- Status
-
vulnerable
Custom Field Template # CVE-2023-38392
- CVE, Research URL
- Home page URL
- Application
- Date
- Aug 07, 2023
- Research Description
- Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Hiroaki Miyashita Custom Field Template plugin <= 2.5.9 versions.
- Affected versions
-
max 2.6.0.
- Status
-
vulnerable
Custom Field Template # CVE-2024-25919
- CVE, Research URL
- Home page URL
- Application
- Date
- Mar 15, 2024
- Research Description
- 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 versions
-
max 2.6.1.
- Status
-
vulnerable
Custom Field Template # 9b1f4dd8b48b1cf7e3a6c0bace0834e92dad8bbd
- CVE, Research URL
- Home page URL
- Application
- Date
- Sep 16, 2020
- Research Description
- Custom Field Template [custom-field-template] < 2.5.2 WordPress Custom Field Template plugin <= 2.5.1 - Cross-Site Request Forgery (CSRF) vulnerability Cross-Site Request Forgery (CSRF) vulnerability found by Jerome Bruandet (NinTechNet) in WordPress Custom Field Template plugin (versions <= 2.5.1).
- Affected versions
-
max 2.5.2.
- Status
-
vulnerable
Custom Field Template # CVE-2022-4324
- CVE, Research URL
- Home page URL
- Application
- Date
- Jan 03, 2023
- Research Description
- 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 versions
-
max 2.5.8.
- Status
-
vulnerable
Custom Field Template # CVE-2023-22695
- CVE, Research URL
- Home page URL
- Application
- Date
- Jul 10, 2023
- Research Description
- Cross-Site Request Forgery (CSRF) vulnerability in Hiroaki Miyashita Custom Field Template plugin <= 2.5.8 versions.
- Affected versions
-
max 2.5.9.
- Status
-
vulnerable
Jun 14, 2024
Custom Field Template # CVE-2023-6748
- CVE, Research URL
- Home page URL
- Application
- Date
- Jun 11, 2024
- Research Description
- 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 versions
-
max 2.6.2.
- Status
-
vulnerable
Custom Field Template # CVE-2023-6745
- CVE, Research URL
- Home page URL
- Application
- Date
- Jun 11, 2024
- Research Description
- 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 contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
- Affected versions
-
max 2.6.2.
- Status
-
vulnerable
Custom Field Template # CVE-2024-0653
- CVE, Research URL
- Home page URL
- Application
- Date
- Jun 11, 2024
- Research Description
- 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 inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
- Affected versions
-
max 2.6.2.
- Status
-
vulnerable
Custom Field Template # CVE-2024-0627
- CVE, Research URL
- Home page URL
- Application
- Date
- Jun 11, 2024
- Research Description
- 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 with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
- Affected versions
-
max 2.6.2.
- Status
-
vulnerable
Sep 02, 2024
Custom Field Template # CVE-2024-44062
- CVE, Research URL
- Home page URL
- Application
- Date
- Sep 15, 2024
- Research Description
- 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 versions
-
max 2.6.6.
- Status
-
vulnerable
Dec 11, 2025
Custom Field Template # CVE-2025-63058
- CVE, Research URL
- Home page URL
- Application
- Date
- Dec 09, 2025
- Research 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.
- Affected versions
-
max 2.7.7.
- Status
-
vulnerable
Jan 11, 2026
Custom Field Template # CVE-2025-68607
- CVE, Research URL
- Home page URL
- Application
- Date
- Dec 30, 2025
- Research Description
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Hiroaki Miyashita Custom Field Template custom-field-template allows Stored XSS.This issue affects Custom Field Template: from n/a through <= 2.7.7.
- Affected versions
-
max 2.7.8.
- Status
-
vulnerable
Jun 16, 2026
Custom Field Template # e03420c55099714ac90da016761d318e5e1cb6db
- CVE, Research URL
- Home page URL
- Application
- Date
- -
- Research Description
- Custom Field Template [custom-field-template] < 2.5.2 404 Page Not Found
- Affected versions
-
max 2.5.2.
- Status
-
vulnerable
Custom Field Template # aa47a464-af97-43bc-b6cb-75a08ce3ece7
- CVE, Research URL
- Home page URL
- Application
- Date
- -
- Research Description
- Custom Field Template [custom-field-template] < 2.5.2 Multiple Plugins/Themes - Cross-Site Request Forgery (CSRF) 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 versions
-
max 2.5.2.
- Status
-
vulnerable
Jul 01, 2026
Custom Field Template # CVE-2026-57687
- CVE, Research URL
- Home page URL
- Application
- Date
- Jul 02, 2026
- Research Description
- Contributor SQL Injection in Custom Field Template <= 2.7.8 versions.
- Affected versions
-
max 2.8.
- Status
-
vulnerable
Sep 20, 2026
Custom Field Template # CVE-2026-9855
- CVE, Research URL
- Home page URL
- Application
- Date
- Sep 19, 2026
- Research Description
- The Custom Field Template plugin for WordPress is vulnerable to generic SQL Injection via the 'post_ID' parameter in all 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 access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The capability check via current_user_can('edit_post', $id) is bypassable because WordPress internally casts $id to an integer for the permission evaluation while the full unsanitized string is preserved and passed to the SQL sink, and a valid nonce — which is also required — can be legitimately obtained by any Contributor-level user from the post edit screen.
- Affected versions
-
max 2.8.
- Status
-
vulnerable
Sep 23, 2026
Custom Field Template # CVE-2026-12995
- CVE, Research URL
- Home page URL
- Application
- Date
- Sep 22, 2026
- Research Description
- The Custom Field Template plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.7.8 via the edit_meta_value due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to delete arbitrary media attachments site-wide by supplying any numeric attachment ID in the file-field parameter alongside the corresponding delete flag, causing content loss and broken pages. Exploitation requires that the attacker's post is governed by a Custom Field Template containing at least one file-type field with the mediaRemove option not enabled, which is the default configuration for file fields.
- Affected versions
-
max 2.8.
- Status
-
vulnerable