Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: `loginok.html` leaks the local installation path via an error message. 💥 **Consequences**: Information Disclosure (CWE-209).…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: Improper validation of the `UID` session cookie. 🔍 **Flaw**: Supplying an overlong `UID` value triggers a server error that exposes the full local filesystem path.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: Wing FTP Server. 📉 **Versions**: All versions **prior to 7.4.4**. 🏢 **Vendor**: wftpserver.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Hackers Can**: Disclose the local file system path. 🧩 **Impact**: This info aids in chaining attacks (e.g., CVE-2025-47812). It does NOT directly grant RCE but enables it.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚠️ **Threshold**: Medium. 📝 **Auth**: Requires **Authentication** (PR:L). 🌐 **Access**: Network accessible (AV:N). 🚫 **UI**: No user interaction needed (UI:N).

Question 6

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

Accepted Answer

📜 **Public Exp**: Yes. 🧪 **PoC**: Available via Nuclei templates (projectdiscovery). 🔗 **Link**: `http/cves/2025/CVE-2025-47813.yaml`. 🌍 **Wild Exp**: Low complexity, but auth required.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**: Send a malformed/overlong `UID` cookie to `/loginok.html`. 👀 **Indicator**: Look for error responses containing the full local filesystem path.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🛠️ **Fixed**: Yes. ✅ **Patch**: Upgrade to **Wing FTP Server 7.4.4** or later. 📅 **Published**: 2025-07-10.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch?**: Restrict access to `/loginok.html`. 🔒 **Mitigation**: Ensure strict input validation for `UID` cookies. 🛑 **Block**: Limit network exposure if possible.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: High Priority. 📈 **CVSS**: 5.3 (Medium). ⚡ **Reason**: Authenticated info disclosure is a stepping stone to RCE. Patch immediately to prevent chaining attacks.

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

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