HomeWordPress vulnerabilitiesCustom Field Template
Custom Field Template vulnerabilities
Custom Field Template has 8 known vulnerabilities in this database. The most recent published record is dated 22 Sep 2026.
- Known vulnerabilities
- 8
- Active installs
- 30,000+
- Latest version
- 2.8.1
- Last updated
- 11 Aug 2026
- Most recent
- 22 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-12995 | Medium 4.3 | Up to 2.7.8 | Fixed in a later version (latest 2.8.1) | 22 Sep 2026 |
| SQL injection CVE-2026-9855 | Medium 6.5 | Up to 2.7.8 | Fixed in a later version (latest 2.8.1) | 19 Sep 2026 |
| Cross-site scripting (XSS) CVE-2023-6745 | Medium 6.4 | Before 2.6.2 | Fixed in 2.6.2 | 11 Jun 2024 |
| Sensitive data exposure CVE-2023-6748 | Medium 4.3 | Before 2.6.2 | Fixed in 2.6.2 | 11 Jun 2024 |
| Cross-site scripting (XSS) CVE-2024-0627 | Medium 6.4 | Before 2.6.2 | Fixed in 2.6.2 | 11 Jun 2024 |
| Cross-site scripting (XSS) CVE-2024-0653 | Medium 4.4 | Before 2.6.2 | Fixed in 2.6.2 | 11 Jun 2024 |
| Cross-site request forgery (CSRF) CVE-2020-36742 | Medium 4.3 | Up to 2.5.1 | Fixed in a later version (latest 2.8.1) | 1 Jul 2023 |
| PHP object injection CVE-2022-4324 | High 7.2 | Before 2.5.8 | Fixed in 2.5.8 | 2 Jan 2023 |
Read the published descriptions
- CVE-2026-12995, 22 Sep 2026
- 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. CVE record
- CVE-2026-9855, 19 Sep 2026
- 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. CVE record
- CVE-2023-6745, 11 Jun 2024
- 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. CVE record
- CVE-2023-6748, 11 Jun 2024
- 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. CVE record
- CVE-2024-0627, 11 Jun 2024
- 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. CVE record
- CVE-2024-0653, 11 Jun 2024
- 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. CVE record
- CVE-2020-36742, 1 Jul 2023
- 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. CVE record
- CVE-2022-4324, 2 Jan 2023
- 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. CVE record
What to do if you run Custom Field Template
If you run Custom Field Template, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Custom Field Template vulnerabilities
Free. We email you when a new vulnerability is published for Custom Field Template, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.