# CVE-2025-70841: Information disclosure in n/a

> Unauthenticated attackers can access exposed .env files to steal credentials and keys, leading to full system compromise and tenant data theft.

- **Severity:** Critical 10.0 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-3x28-p955-cr3v

## What is CVE-2025-70841?

CVE-2025-70841 is a critical vulnerability in n/a, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dokans Multi-Tenancy Based eCommerce Platform SaaS 3.9.2 allows unauthenticated remote attackers to obtain sensitive application configuration data via direct request to /script/.env file. The exposed file contains Laravel application encryption key (APP_KEY), database credentials, SMTP/SendGrid API credentials, and internal configuration parameters, enabling complete system compromise including authentication bypass via session token forgery, direct database access to all tenant data, and email infrastructure takeover. Due to the multi-tenancy architecture, this vulnerability affects all tenants in the system.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-70841?

It affects 1 product.


Products: Amcoders Dokans.

## How do I fix CVE-2025-70841?

No fix has been published for CVE-2025-70841 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-70841 being exploited?

There is no known exploitation of CVE-2025-70841 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70841 and fix it if it is affected.

What it is: CVE-2025-70841 is a critical vulnerability in n/a, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-70841 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-70841/ (Markdown: https://insights.sbomify.com/CVE-2025-70841/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-70841
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-70841
- OSV: https://osv.dev/vulnerability/CVE-2025-70841

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-70841/
Summaries are generated and may contain mistakes; the official description above is the record.