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.
References10
- plugins.trac.wordpress.org/browser/custom-field-template/tags/2…
- plugins.trac.wordpress.org/browser/custom-field-template/tags/2…
- plugins.trac.wordpress.org/browser/custom-field-template/tags/2…
- plugins.trac.wordpress.org/browser/custom-field-template/tags/2…
- plugins.trac.wordpress.org/browser/custom-field-template/tags/2…
- plugins.trac.wordpress.org/browser/custom-field-template/tags/2…
- plugins.trac.wordpress.org/browser/custom-field-template/tags/2…
- plugins.trac.wordpress.org/browser/custom-field-template/tags/2…
- plugins.trac.wordpress.org/changeset?reponame=&old=3589466%40cu…
- www.wordfence.com/threat-intel/vulnerabilities/id/ce924708-935a…
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 1% percentile: 48 · as of 8 November 2026
- CWE
- CWE-89
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.