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.
Published: 2026-09-19
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Data Exfiltration
Action: Apply Patch
AI Analysis

Impact

Custom Field Template for WordPress allows contributors and higher roles to trigger SQL injection through the post_ID parameter. The plugin fails to escape this user‑supplied value and does not prepare the surrounding SQL query, enabling an attacker to append additional statements. Permission checks are bypassed because WordPress internally casts the post ID to an integer for the capability test while the original, unsanitized string is still sent to the database engine. A valid nonce, obtainable from the post edit screen, enables the injection with no other surface needed.

Affected Systems

WordPress sites running Custom Field Template version 2.7.8 or earlier are impacted. The vulnerability is present in all releases up to and including 2.7.8; later versions are presumed fixed and are not affected.

Risk and Exploitability

The CVSS score of 6.5 indicates a moderate severity. The EPSS score is less than 1 %, suggesting a low probability of exploitation at this time, and the vulnerability is not listed in the CISA KEV catalog. Nevertheless, authenticated users with contributor or higher access can read sensitive database information, so the risk exists wherever such roles are assigned and the susceptible plugin version is active.

Generated by OpenCVE AI on September 19, 2026 at 23:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Custom Field Template to version 2.7.9 or later, which resolves the SQL injection flaw.
  • If an upgrade is not immediately possible, remove the plugin from active use or replace it with a verified alternative that does not expose the vulnerable parameter.
  • Restrict contributor and higher roles from editing posts until the plugin is removed or upgraded, to reduce the attack surface while a fix is applied.

Generated by OpenCVE AI on September 19, 2026 at 23:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 20 Sep 2026 01:30:00 +0000

Type Values Removed Values Added
First Time appeared Hiroaki Miyashita
Hiroaki Miyashita custom Field Template
Wordpress
Wordpress wordpress
Vendors & Products Hiroaki Miyashita
Hiroaki Miyashita custom Field Template
Wordpress
Wordpress wordpress

Sat, 19 Sep 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Sat, 19 Sep 2026 08:00:00 +0000

Type Values Removed Values Added
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.
Title Custom Field Template <= 2.7.8 - Authenticated (Contributor+) SQL Injection via 'post_ID' Parameter
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

Subscriptions

Hiroaki Miyashita Custom Field Template
Wordpress Wordpress
cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-09-19T13:51:20.741Z

Reserved: 2026-05-28T15:31:05.357Z

Link: CVE-2026-9855

cve-icon Vulnrichment

Updated: 2026-09-19T13:50:53.149Z

cve-icon NVD

Status : Deferred

Published: 2026-09-19T08:16:55.487

Modified: 2026-09-21T13:33:33.387

Link: CVE-2026-9855

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-20T01:15:06Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')