What is the CVSS score of CVE-2025-70841?

CVE-2025-70841 has a CVSS 3.1 base score of 10.0 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2025-70841?

Yes, a public proof-of-concept exploit is available for CVE-2025-70841. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-70841?

Within 24 hours: Take affected systems offline or restrict network access to the application, immediately audit logs for unauthorized access to /.env and related endpoints, and notify your incident response team and legal/compliance departments. Within 7 days: Rotate all exposed credentials (database passwords, API keys, secrets), conduct forensic analysis to determine scope of unauthorized access, and identify an upgrade or replacement platform. Within 30 days: Complete migration away from v3.9.2 to a patched version when available, perform full security assessment of exposed systems, and implement preventive controls to block direct access to configuration files.

Dokans CVE-2025-70841

CRITICAL

Improper Authentication (CWE-287)

2026-02-03 cve@mitre.org

Authentication Bypass Laravel Dokans

10.0

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-287 OWASP Top 10:2025 A07:2025 - Authentication Failures ASVS 5.0 V6 - Authentication Authentication mechanism validation MITRE ATT&CK 2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	CVSS 10.0 with PoC — maximum severity. Multi-tenant SaaS platforms contain data for multiple businesses. Compromise exposes all tenants' data simultaneously.
Exploit ScenarioDerived	An attacker exploits the authentication bypass to access the Dokans admin interface, extracting API keys, payment gateway credentials, and customer data from all tenants on the platform.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Dokans SaaS e-commerce platform v3.9.2 has a CVSS 10.0 authentication bypass allowing unauthenticated attackers to obtain sensitive application secrets and tenant data.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:54 CVSS 10.0

CVSS 10.0 authentication bypass in Dokans SaaS exposes tenant secrets and application data.

RemediationAI

Update immediately. Rotate all API keys and payment credentials. Notify affected tenants.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Dokans Multi-Tenancy Based eCommerce Platform SaaS v3.9.2 has a CWE-287 authentication bypass that allows unauthenticated remote attackers to access sensitive application secrets, API keys, and tenant-specific data.

Know when Dokans gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 10.0 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

PoC Detected

Feb 11, 2026 - 15:58 vuln.today

Public exploit code

CVE Published

Feb 03, 2026 - 18:16 nvd

CRITICAL 10.0

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A critical vulnerability in Dokans eCommerce Platform v3.9.2 exposes sensitive application configuration data, including database credentials and API keys, to unauthenticated attackers without requiring specialized exploits. Any organization running this version faces immediate risk of data breach, system compromise, and potential lateral movement into connected infrastructure.

Business Impact: Severe

Compensating Controls

Implement Web Application Firewall (WAF) rules to block all requests to /.env, /script/.env, and other configuration file paths with HTTP 403 responses; restrict network access to the application via IP whitelisting or VPN; disable directory listing and implement strict access controls on script directories; enable robust authentication and rate limiting; monitor access logs for suspicious requests to configuration endpoints; consider using a reverse proxy to strip sensitive paths before they reach the application; rotate all secrets immediately and store future secrets in a dedicated vault external to the application.

Threat Intelligence Overview

EPSS Score

0.1%

Top 74% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.1%

Patch available No

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.