CVE-2025-60174 — AI Deep Analysis Summary

Q: What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Untrusted data deserialization in WP Gravity Forms Constant Contact Plugin. 💥 **Consequences**: Object injection leading to full system compromise. Critical integrity & confidentiality loss.

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: CWE-502 (Deserialization of Untrusted Data). 🐛 **Flaw**: The plugin processes external inputs without proper validation before deserializing them into objects.

Q: Who is affected? (Versions/Components)

📦 **Affected**: WordPress Plugin 'WP Gravity Forms Constant Contact Plugin'. 📅 **Versions**: 1.1.2 and earlier. 🏢 **Vendor**: CRM Perks.

Q: What can hackers do? (Privileges/Data)

🕵️ **Hacker Actions**: Arbitrary object injection. 📊 **Impact**: High (H) Confidentiality, Integrity, & Availability loss. Potential RCE (Remote Code Execution) via crafted serialized payloads.

Q: Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: LOW. 🚫 **Auth**: None required (PR:N). 🖱️ **UI**: None required (UI:N). 🌐 **Network**: Remote (AV:N). Easy to exploit remotely.

Q: Is there a public Exp? (PoC/Wild Exploitation)

📜 **Public Exp?**: No specific PoC provided in data (pocs: []). ⚠️ **Risk**: High likelihood of wild exploitation due to low complexity (AC:L) and no auth requirement.

Q: How to self-check? (Features/Scanning)

🔍 **Check**: Scan for 'WP Gravity Forms Constant Contact Plugin' version <= 1.1.2. 📡 **Tools**: Use vulnerability scanners targeting CWE-502 in WordPress plugins. Check installed plugin list in WP admin.

Q: Is it fixed officially? (Patch/Mitigation)

🩹 **Fix**: Update plugin to version > 1.1.2. 📢 **Source**: Vendor 'CRM Perks' released patch. Reference: Patchstack database entry.

Q: What if no patch? (Workaround)

🚧 **Workaround**: Disable the plugin immediately if patching isn't possible. 🛑 **Mitigation**: Remove the plugin directory or deactivate via WP admin to block the deserialization vector.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: CRITICAL. 🚀 **Priority**: Patch IMMEDIATELY. CVSS Score is High (9.8 implied by H/H/H). Remote, unauthenticated exploitation makes this a top-priority fix.

Updated May 06, 2026 CVSS 9.8 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Untrusted data deserialization in WP Gravity Forms Constant Contact Plugin. 💥 **Consequences**: Object injection leading to full system compromise. Critical integrity & confidentiality loss.

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: CWE-502 (Deserialization of Untrusted Data). 🐛 **Flaw**: The plugin processes external inputs without proper validation before deserializing them into objects.

Q3Who is affected? (Versions/Components)

📦 **Affected**: WordPress Plugin 'WP Gravity Forms Constant Contact Plugin'. 📅 **Versions**: 1.1.2 and earlier. 🏢 **Vendor**: CRM Perks.

Q4What can hackers do? (Privileges/Data)

🕵️ **Hacker Actions**: Arbitrary object injection. 📊 **Impact**: High (H) Confidentiality, Integrity, & Availability loss. Potential RCE (Remote Code Execution) via crafted serialized payloads.

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: LOW. 🚫 **Auth**: None required (PR:N). 🖱️ **UI**: None required (UI:N). 🌐 **Network**: Remote (AV:N). Easy to exploit remotely.

Q6Is there a public Exp? (PoC/Wild Exploitation)

📜 **Public Exp?**: No specific PoC provided in data (pocs: []). ⚠️ **Risk**: High likelihood of wild exploitation due to low complexity (AC:L) and no auth requirement.

Q7How to self-check? (Features/Scanning)

🔍 **Check**: Scan for 'WP Gravity Forms Constant Contact Plugin' version <= 1.1.2. 📡 **Tools**: Use vulnerability scanners targeting CWE-502 in WordPress plugins. Check installed plugin list in WP admin.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix**: Update plugin to version > 1.1.2. 📢 **Source**: Vendor 'CRM Perks' released patch. Reference: Patchstack database entry.

Q9What if no patch? (Workaround)

🚧 **Workaround**: Disable the plugin immediately if patching isn't possible. 🛑 **Mitigation**: Remove the plugin directory or deactivate via WP admin to block the deserialization vector.

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: CRITICAL. 🚀 **Priority**: Patch IMMEDIATELY. CVSS Score is High (9.8 implied by H/H/H). Remote, unauthenticated exploitation makes this a top-priority fix.

Continue exploring

Vulnerability detail Full AI analysis (login) CRM Perks CWE-502