# CVE-2025-30673: Sub::HandlesVia for Perl allows untrusted code to be included from the current working directory

> Attackers can execute arbitrary code by placing malicious files in the current working directory, affecting Perl applications using Sub::HandlesVia.

- **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:** Yes
- **Published:** 1 Apr 2025
- **Updated:** 1 Apr 2025
- **Also known as:** DEBIAN-CVE-2025-30673, GHSA-hhc7-9jf4-whgx, UBUNTU-CVE-2025-30673

## What is CVE-2025-30673?

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

### Official description

Sub::HandlesVia for Perl before 0.050002 allows untrusted code from the current working directory ('.') to be loaded 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.

Sub::HandlesVia uses Mite to produce the affected code section due to CVE-2025-30672

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

Upgrade to a fixed version.

## Is CVE-2025-30673 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30673 is a medium-severity code injection vulnerability in TOBYINK Sub::HandlesVia, 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-30673 in the wild and no public exploit code.

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

## Sources

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

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