# CVE-2024-25677: Security feature bypass in n/a

> Min browser fails to treat local files as unique origins, allowing local files to improperly request cross-origin resources.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2024
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-4w9v-7h8h-rv8x, GHSA-xw9w-mmhr-225x

## What is CVE-2024-25677?

CVE-2024-25677 is a high-severity vulnerability in n/a, published on 9 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Min before 1.31.0, local files are not correctly treated as unique security origins, which allows them to improperly request cross-origin resources. For example, a local file may request other local files through an XML document.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-25677?

It affects 1 product.


Products: Minbrowser Min.

## How do I fix CVE-2024-25677?

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

## Is CVE-2024-25677 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25677 and fix it if it is affected.

What it is: CVE-2024-25677 is a high-severity vulnerability in n/a, published on 9 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25677 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-2024-25677/ (Markdown: https://insights.sbomify.com/CVE-2024-25677/index.md)
```

## Sources

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

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