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

6.5
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE CVE-2026-9855
CVSS 6.5 (Medium)
Publicly Published September 18, 2026
Last Updated September 19, 2026
Researcher Luc Huynh from Noventiq RedTeam - Noventiq Vietnam

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.

Learn more about SQL Injection vulnerabilities and how to prevent them.

References

Share

Vulnerability Details for Custom Field Template

Software Type Plugin
Software Slug custom-field-template (view on wordpress.org)
Patched? Yes
Remediation Update to version 2.8, or a newer patched version
Affected Version
  • <= 2.7.8
Patched Version
  • 2.8

Recent vulnerabilities in Custom Field Template

# Title CVE ID CVSS Researchers Date
1 Custom Field Template <= 2.7.8 - Authenticated (Contributor+) Insecure Direct Object Reference to Arbitrary Media File Deletion via 'file_field' Parameter CVE-2026-12995 4.3 Dmitrii Ignatyev September 21, 2026
2 Custom Field Template <= 2.7.8 - Authenticated (Contributor+) SQL Injection CVE-2026-57687 6.5 daroo June 29, 2026
3 Custom Field Template <= 2.7.7 - Authenticated (Contributor+) Stored Cross-Site Scripting CVE-2025-68607 6.4 Muhammad Yudha - DJ December 24, 2025
4 Custom Field Template <= 2.7.6 - Authenticated (Subscriber+) Information Exposure CVE-2025-63058 4.3 Phat RiO December 8, 2025
5 Custom Field Template <= 2.6.5 - Authenticated (Contributor+) Stored Cross-Site Scripting CVE-2024-44062 6.4 Robert DeVore August 29, 2024
6 Custom Field Template <= 2.6.1 - Authenticated (Admin+) Stored Cross-Site Scritping CVE-2024-0653 4.4 catfather June 10, 2024
7 Custom Field Template <= 2.6.1 - Authenticated(Contributor+) Information Exposure CVE-2023-6748 4.3 Francesco Carlucci June 10, 2024
8 Custom Field Template <= 2.6.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via shortcode CVE-2023-6745 6.4 Francesco Carlucci June 10, 2024
9 Custom Field Template <= 2.6.1 - Authenticated(Constibutor+) Stored Cross-Site Scripting via Custom Field Name CVE-2024-0627 6.4 Luk 6785 June 10, 2024
10 Custom Field Template <= 2.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via $search_label CVE-2024-25919 6.4 LVT-tholv2k February 14, 2024

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation