# CVE-2018-25030: Mirmay Secure Private Browser / File Manager Auto Lock improper authentication

> A race condition in the Auto Lock feature allows local attackers to bypass authentication in the Mirmay Secure Private Browser and File Manager.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-94ff-64vj-pp8h

## What is CVE-2018-25030?

CVE-2018-25030 is a low-severity vulnerability in Mirmay File Manager, published on 28 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in Mirmay Secure Private Browser and File Manager up to 2.5. Affected is the Auto Lock. A race condition leads to a local authentication bypass. The exploit has been disclosed to the public and may be used.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-25030?

It affects 2 products.


Products: Mirmay File Manager, Mirmay Secure Private Browser.

## How do I fix CVE-2018-25030?

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

## Is CVE-2018-25030 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25030 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25030 and fix it if it is affected.

What it is: CVE-2018-25030 is a low-severity vulnerability in Mirmay File Manager, published on 28 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25030 exists.

Affected product: Mirmay File Manager. 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-2018-25030/ (Markdown: https://insights.sbomify.com/CVE-2018-25030/index.md)
```

## Sources

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

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