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

✅ **Fix**: Update the plugin to version **2.1.4 or later**. <br>📥 **Source**: Official WordPress plugin repository or vendor patchstack link. <br>🔄 **Action**: Immediate update is the primary mitigation.

Q: Is it urgent? (Priority Suggestion)

🔥 **Priority**: **CRITICAL**. <br>🚨 **CVSS**: **9.8** (High). <br>⏳ **Urgency**: Patch immediately. The combination of no auth required and high impact makes this a top-priority target for attackers.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: A critical privilege escalation flaw in the Directorist Social Login plugin.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-266** (Incorrect Privilege Assignment).
🔍 **Flaw**: The plugin fails to properly verify user permissions, allowing lower-privileged users to execute high-level functions.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: WordPress Plugin **Directorist Social Login**.
📉 **Version**: Versions **prior to 2.1.4** are vulnerable.
🏢 **Vendor**: Directorist.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

👑 **Privileges**: Attackers gain **High** impact on Confidentiality, Integrity, and Availability.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚡ **Threshold**: **Low**.
🌐 **Network**: Attack Vector is **Network** (AV:N).
🔑 **Auth**: **No Privileges Required** (PR:N).
👀 **UI**: **No User Interaction** (UI:N).
🎯 **Complexity**: **Low** (AC:L).

Question 6

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

Accepted Answer

🧪 **Exploit**: No public PoC or Exploit code is currently listed in the provided data.
⚠️ **Risk**: Despite no public code, the low exploitation barrier makes it highly susceptible to automated attacks.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Check**: Scan for **Directorist Social Login** plugin.
📊 **Version**: Verify if installed version is **< 2.1.4**.
🛠️ **Tool**: Use WordPress vulnerability scanners or check plugin settings for version info.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fix**: Update the plugin to version **2.1.4 or later**.
📥 **Source**: Official WordPress plugin repository or vendor patchstack link.
🔄 **Action**: Immediate update is the primary mitigation.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **Workaround**: If updating is impossible, **deactivate and delete** the plugin immediately.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Priority**: **CRITICAL**.
🚨 **CVSS**: **9.8** (High).
⏳ **Urgency**: Patch immediately. The combination of no auth required and high impact makes this a top-priority target for attackers.

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

CVE-2026-22337 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

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

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring