CVE-2024-44062

6.5 MEDIUM

📋 TL;DR

This vulnerability allows attackers to inject malicious scripts into WordPress sites using the Custom Field Template plugin. When executed, these scripts can steal user sessions, deface websites, or redirect visitors to malicious sites. All WordPress sites running Custom Field Template version 2.6.5 or earlier are affected.

💻 Affected Systems

Products:
  • WordPress Custom Field Template plugin
Versions: All versions up to and including 2.6.5
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires the plugin to be installed and active on a WordPress site. No special configuration needed for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator credentials, take full control of the WordPress site, install backdoors, or compromise all visitor data.

🟠

Likely Case

Attackers inject malicious JavaScript that steals user session cookies, allowing account takeover of logged-in users including administrators.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts would be neutralized before execution, preventing any impact.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires contributor-level access or higher to inject malicious scripts into stored content.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.6.6

Vendor Advisory: https://patchstack.com/database/vulnerability/custom-field-template/wordpress-custom-field-template-plugin-2-6-5-cross-site-scripting-xss-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find Custom Field Template and click 'Update Now'. 4. Verify version shows 2.6.6 or higher.

🔧 Temporary Workarounds

Disable plugin

all

Temporarily disable the Custom Field Template plugin until patched

wp plugin deactivate custom-field-template

Restrict user roles

all

Limit contributor and author access to prevent script injection

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block XSS payloads
  • Enable Content Security Policy (CSP) headers to restrict script execution

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for Custom Field Template version

Check Version:

wp plugin get custom-field-template --field=version

Verify Fix Applied:

Verify plugin version is 2.6.6 or higher in WordPress admin

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to plugin admin pages
  • JavaScript injection patterns in form submissions

Network Indicators:

  • Malicious script tags in HTTP requests to WordPress admin

SIEM Query:

source="wordpress.log" AND "custom-field-template" AND ("script" OR "javascript" OR "onload" OR "onerror")

🔗 References

📤 Share & Export