Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2025-28983 — AI Deep Analysis Summary

CVSS 9.8 · Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: SQL Injection (SQLi) in Click & Pledge Connect plugin. <br>💥 **Consequences**: Attackers can manipulate database queries, leading to **Privilege Escalation** and full system compromise.…

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-89** (Improper Neutralization of Special Elements used in an SQL Command).…

Q3Who is affected? (Versions/Components)

🏢 **Vendor**: ClickandPledge. <br>📦 **Product**: Click & Pledge Connect. <br>📅 **Affected Versions**: WordPress **6.8** and earlier versions. ⚠️ If you are on 6.8 or below, you are vulnerable.

Q4What can hackers do? (Privileges/Data)

🕵️ **Hackers Can**: <br>1. **Escalate Privileges**: Gain admin access. <br>2. **Steal Data**: Extract sensitive database info. <br>3. **Modify Content**: Alter site data.…

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. <br>🌐 **Vector**: Network (AV:N). <br>🔑 **Auth**: None required (PR:N). <br>👀 **UI**: None required (UI:N). <br>✅ **Ease**: Easy to exploit remotely without authentication.

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

📜 **Public Exploit**: **No** specific PoC provided in the data (pocs: []). <br>🌍 **Wild Exploitation**: Likely possible due to low complexity (AC:L) and no auth requirement. Treat as **active threat**.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1. Check WordPress Plugin list for **Click & Pledge Connect**. <br>2. Verify version is **≤ 6.8**. <br>3. Scan for SQLi patterns in plugin endpoints. <br>🛠️ Use automated scanners targeting CWE-89.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix Status**: Patch available via vendor. <br>🔗 **Reference**: Patchstack database entry confirms fix. <br>✅ **Action**: Update plugin to the latest version immediately. Official patch exists.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: <br>1. **Disable** the plugin if not essential. <br>2. **Restrict Access**: Limit plugin functionality via firewall rules. <br>3.…

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. <br>📊 **CVSS**: High (H/H/H). <br>🚀 **Priority**: **Immediate Action Required**. <br>📢 Deploy patch or disable plugin NOW to prevent privilege escalation attacks.