CVE-2026-9855 json
Custom Field Template <= 2.7.8 - Authenticated (Contributor+) SQL Injection via 'post_ID' Parameter
published last mo. modified last mo. also EUVD-2026-83557
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-9855 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- hiroaki-miyashita Custom Field Template
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/ce924708-935a-45c0-8959-dd122632cef4?source=cve
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.8/custom-field-template.php#L4442
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.8/custom-field-template.php#L3353
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.8/custom-field-template.php#L3479
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.8/custom-field-template.php#L105
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.7/custom-field-template.php#L4442
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.7/custom-field-template.php#L3353
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.7/custom-field-template.php#L3479
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.7/custom-field-template.php#L105
- plugins.trac.wordpress.org /changeset?reponame=&old=3589466%40custom-field-template&new=3589466%40custom-field-template
Sources
- CVE List CVE-2026-9855
- NVD CVE-2026-9855
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.