Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2025-70841 β€” AI Deep Analysis Summary

CVSS 10.0 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Direct request to `/script/.env` leaks sensitive config data. πŸ’₯ **Consequences**: Full system compromise, tenant DB access, email infrastructure takeover.

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: Information Disclosure via insecure file access. The `.env` file is directly accessible, exposing secrets. (CWE not specified in data).

Q3Who is affected? (Versions/Components)

πŸ“¦ **Affected**: **Dokans** (AMCoders e-commerce platform). Specifically **Version 3.9.2**. 🌐 SaaS/Multitenancy architecture.

Q4What can hackers do? (Privileges/Data)

πŸ•΅οΈ **Attacker Actions**: 1. Bypass auth via session token forgery. 2. Access **all tenant databases**. 3. Take over **email infrastructure**. 4. Complete system control.

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **Threshold**: **LOW**. CVSS: `AV:N` (Network), `AC:L` (Low Complexity), `PR:N` (No Privs), `UI:N` (No User Interaction). Easy to exploit remotely.

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

πŸ’» **Exploit Status**: No public PoC listed in data (`pocs: []`). However, GitHub advisory exists. Wild exploitation likely possible given low barrier.

Q7How to self-check? (Features/Scanning)

πŸ” **Self-Check**: Scan for direct HTTP GET requests to `/script/.env`. Check if server returns environment variables or config secrets. Use automated scanners for `.env` exposure.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix Status**: Data does not list a specific patch version. Reference links point to Codecanyon and GitHub advisory. Check vendor for update.

Q9What if no patch? (Workaround)

🚧 **Workaround**: Block direct access to `/script/.env` via Web Application Firewall (WAF) or Nginx/Apache config. Restrict file permissions. Rotate all exposed credentials immediately.

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Urgency**: **CRITICAL**. CVSS Score implies High Impact (`C:H`, `I:H`). Immediate action required to prevent data breach and system takeover. Patch or mitigate ASAP.