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

🔍 **Self-Check**: 1️⃣ Verify app version is **< 20251103**. 2️⃣ Audit API endpoints for **user-controlled key injection**. 3️⃣ Monitor logs for **unauthorized access patterns** or parameter anomalies.

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

🛠️ **Official Fix**: Patch released on **2025-11-03**. 📝 **Reference**: USOM Advisory (tr-25-0371). ✅ **Action**: Update to the latest version immediately to close the authorization bypass.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. 📊 **CVSS**: High severity (C:H, I:H). ⚡ **Priority**: Immediate patching required. The low exploitation complexity makes it a prime target for attackers.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: CVE-2025-0987 is a critical flaw in **CB Project CVLand**. It allows **authorization bypass** due to user-controlled keys.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-639** (Authorization Bypass Through User-Controlled Key).…

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📱 **Affected Product**: **CB Project CVLand** (Recruitment Mobile App by CB Project Ltd. Co.).
📅 **Versions**: **2.1.0** through **20251103**.
🌍 **Vendor**: Turkish company CB Project.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

💀 **Attacker Actions**:
1️⃣ **Bypass Auth**: Gain unauthorized access without valid credentials.
2️⃣ **Parameter Injection**: Manipulate backend parameters.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

🔑 **Exploitation Threshold**:
✅ **Network**: Remote (AV:N).
✅ **Complexity**: Low (AC:L).
⚠️ **Privileges**: Requires **Low Privileges** (PR:L) to initiate.
👁️ **UI**: No User Interaction needed (UI:N).

Question 6

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

Accepted Answer

🚫 **Public Exploit**: **No**.
📂 **PoCs**: None listed in current data.
⏳ **Status**: Theoretical risk based on CVSS analysis. No wild exploitation confirmed yet.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**:
1️⃣ Verify app version is **< 20251103**.
2️⃣ Audit API endpoints for **user-controlled key injection**.
3️⃣ Monitor logs for **unauthorized access patterns** or parameter anomalies.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🛠️ **Official Fix**: Patch released on **2025-11-03**.
📝 **Reference**: USOM Advisory (tr-25-0371).
✅ **Action**: Update to the latest version immediately to close the authorization bypass.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch Workaround**:
1️⃣ **Restrict Access**: Limit network access to the app backend.
2️⃣ **Input Validation**: Strictly sanitize and validate all key inputs.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**.
📊 **CVSS**: High severity (C:H, I:H).
⚡ **Priority**: Immediate patching required. The low exploitation complexity makes it a prime target for attackers.

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

CVE-2025-0987 — 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