# CVE-2025-30672: Mite for Perl generates code with an untrusted search path vulnerability

> An attacker can execute arbitrary code by placing a malicious file in the current working directory, which is loaded due to an unsafe search path in Mite for Perl.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2025
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-jx2w-pp8j-qrcj

## What is CVE-2025-30672?

CVE-2025-30672 is a medium-severity code injection vulnerability in TOBYINK Mite, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mite for Perl before 0.013000 generates code with the current working directory ('.') added to the @INC path similar to CVE-2016-1238.

If an attacker can place a malicious file in current working directory, it may be 
loaded instead of the intended file, potentially leading to arbitrary 
code execution.

This affects the Mite distribution itself, and other distributions that contain code generated by Mite.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2025-30672 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30672 is a medium-severity code injection vulnerability in TOBYINK Mite, published on 1 Apr 2025. 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-30672 in the wild and no public exploit code.

Affected product: TOBYINK Mite. 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-30672/ (Markdown: https://insights.sbomify.com/CVE-2025-30672/index.md)
```

## Sources

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

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