dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2025-30673

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Sub::HandlesVia Perl module before version 0.050002 loads untrusted code from the current working directory ('.'), similar to CVE-2016-1238. An attacker who can place a malicious Perl file in the same directory where the application runs could have it loaded instead of the intended module, leading to arbitrary code execution. The vulnerable code is generated using Mite due to CVE-2025-30672.

MitigationUpgrade Sub::HandlesVia to version 0.050002 or later, and ensure the application runs from directories where untrusted actors cannot write files to prevent directory traversal-style module loading attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Sub::HandlesVia version
    Run 'perl -MSub::HandlesVia -e "print $Sub::HandlesVia::VERSION"' or check your cpanfile/cpanfile.snapshot for the installed version
    Affected if Version is earlier than 0.050002 (e.g., 0.050000, 0.049999, or any version below 0.050002)
  2. Identify if Sub::HandlesVia is loaded
    Search your application code for 'use Sub::HandlesVia' or 'require Sub::HandlesVia', or check if any of your dependencies depend on Sub::HandlesVia via 'cpan -D Sub::HandlesVia'
    Affected if Sub::HandlesVia is loaded by your application or any of your direct dependencies
  3. Check for Mite-generated code in your dependencies
    Search for files named 'Mite.pm' or containing 'Mite' in the 'lib' directories of your installed modules, particularly under dependencies that use Sub::HandlesVia
    Affected if Mite-generated code exists in your environment (vulnerable code is generated by Mite per CVE-2025-30672)
  4. Inspect application working directory
    Run your application from a known directory and check if untrusted users can write files to that directory (ls -la /path/to/working/dir)
    Affected if The working directory is writable by untrusted users or the application runs in a shared directory where others can place files

You are affected if Sub::HandlesVia version is below 0.050002, the module is loaded by your application or its dependencies, and the working directory where the application runs is writable by potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Sub::HandlesVia to version 0.050002 or later, and ensure the application runs from directories where untrusted actors cannot write files to prevent directory traversal-style module loading attacks.

Recommended fix Moderate confidence

Sub::HandlesVia version 0.050002 or later

  1. Upgrade Sub::HandlesVia to version 0.050002 or later by running: cpan Sub::HandlesVia or cpanm Sub::HandlesVia
  2. Alternatively, update via your system's package manager if available
  3. Verify the installed version matches or exceeds 0.050002 using: perl -MSub::HandlesVia -e 'print $Sub::HandlesVia::VERSION'

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30673 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30673 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data