CVE-2025-68607

6.5 MEDIUM

📋 TL;DR

This stored cross-site scripting (XSS) vulnerability in the WordPress Custom Field Template plugin allows attackers to inject malicious scripts into web pages. When users view pages containing the malicious content, the scripts execute in their browsers. All WordPress sites using Custom Field Template version 2.7.5 or earlier are affected.

💻 Affected Systems

Products:
  • WordPress Custom Field Template plugin
Versions: n/a through 2.7.5
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with the vulnerable plugin enabled. Attackers need contributor-level access or higher to exploit.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, take over WordPress admin accounts, deface websites, or redirect users to malicious sites.

🟠

Likely Case

Attackers inject malicious JavaScript that steals user session cookies or credentials when users visit compromised pages.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts would be neutralized before reaching users' browsers.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires at least contributor-level WordPress access. Stored XSS vulnerabilities are commonly weaponized in WordPress environments.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.7.6 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/custom-field-template/vulnerability/wordpress-custom-field-template-plugin-2-7-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 update to version 2.7.6 or later.

🔧 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 roles to trusted users only

🧯 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 2.7.5 or earlier

Check Version:

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

Verify Fix Applied:

Verify plugin version is 2.7.6 or later in WordPress admin panel

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to wp-admin/admin-ajax.php with script tags
  • Multiple failed login attempts followed by successful contributor/admin login

Network Indicators:

  • Outbound connections to suspicious domains after visiting specific pages
  • Unusual JavaScript payloads in HTTP requests

SIEM Query:

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

🔗 References

📤 Share & Export