CVE-2026-9855
Received Received - Intake

SQL Injection in Custom Field Template WordPress Plugin

Publication date: 2026-09-19

Last updated on: 2026-09-19

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-19
Last Modified
2026-09-19
Generated
2026-09-20
AI Q&A
2026-09-20
EPSS Evaluated
N/A
NVD
CVE-2026-9855

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
custom_field_template custom_field_template to 2.7.8 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a SQL Injection vulnerability in the Custom Field Template WordPress plugin up to version 2.7.8. It allows authenticated attackers with contributor-level access or higher to inject malicious SQL queries via the 'post_ID' parameter. The issue occurs due to insufficient input sanitization and lack of proper SQL query preparation.

Detection Guidance

This vulnerability requires authenticated access with contributor-level permissions or higher. Detection involves checking for unusual SQL query patterns or unauthorized database access attempts. Review WordPress logs for suspicious queries involving the 'post_ID' parameter. Use tools like WP-CLI to inspect plugin versions and check for the vulnerable Custom Field Template plugin up to 2.7.8.

Impact Analysis

An attacker could exploit this to extract sensitive data from your WordPress database, such as user credentials, personal information, or other confidential data. They could also potentially modify or delete database content if additional vulnerabilities exist.

Compliance Impact

This vulnerability could lead to unauthorized access and exposure of personal data, violating GDPR and HIPAA requirements for data protection and security. Organizations may face compliance violations, fines, or legal consequences if exploited.

Mitigation Strategies

Immediately update the Custom Field Template plugin to the latest version if available. If no update exists, consider disabling the plugin until a patch is released. Ensure all users follow the principle of least privilege, limiting contributor-level access. Monitor database activity for unauthorized queries and implement a Web Application Firewall (WAF) to block SQL injection attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-9855. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart