PatchTheCVEcustom field template vulnerabilities and fixes
Recent CVEs affecting custom field template, with upgrade or downgrade steps. 8 tracked.
Also searched as: customfieldtemplate.
custom field template has 8 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 8. Most recent: 2024-09-15. Highest priority: CVE-2023-38392 (score 34/100).
- CVE-2024-44062 MEDIUM 6.5 UPGRADE Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in H
- CVE-2024-0653 MEDIUM 4.4 UPGRADE The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings
- CVE-2024-0627 MEDIUM 6.4 UPGRADE The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's c
- CVE-2023-6748 MEDIUM 4.3 UPGRADE The Custom Field Template plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions
- CVE-2023-6745 MEDIUM 6.4 UPGRADE The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's '
- CVE-2023-38392 HIGH 7.1 UPGRADE Unauth
- CVE-2023-22695 MEDIUM 4.3 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in Hiroaki Miyashita Custom Field Template plugin <= 2.5.8 ver
- CVE-2020-36742 MEDIUM 4.3 UPGRADE The Custom Field Template plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to,
FAQ
How do I fix custom field template vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is custom field template being exploited right now?
None of the tracked custom field template CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which custom field template CVE should I patch first?
CVE-2023-38392 currently ranks highest (34/100): Unauth.