CVE-2025-30672
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 · uneditedMite 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.
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 confidenceMite for Perl before 0.013000 generates code that adds the current working directory ('.') to Perl's @INC array, similar to CVE-2016-1238. This allows an attacker who can place a maliciously named Perl module in the working directory where the generated code runs to have it loaded instead of the intended module, achieving arbitrary code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Mite versionRun `perl -MMite::Module -e 'print $Mite::Module::VERSION'` or check your Mite.pm file for the $VERSION variableAffected if The reported version is lower than 0.013000
-
Locate Mite-generated Perl filesSearch your project directory for files containing 'Generated by Mite' or with .mite.pm extension using grep or file search toolsAffected if Mite-generated files exist in the codebase
-
Inspect generated code for @INC manipulationOpen the generated files and search for patterns that add '.' to @INC, such as 'unshift @INC' or 'push @INC' with a dot argumentAffected if Any generated code contains lines that add the current working directory to @INC
You are affected if your installed Mite version is below 0.013000 and any generated code in your environment contains the dangerous practice of adding the current directory to Perl's @INC array
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Mite to version 0.013000 or later to obtain the fixed code generator. Additionally, audit and regenerate any distributions that contain Mite-generated code to ensure the vulnerability is not present in dependent projects.
Mite version 0.013000 or later
- Identify the current installed version of Mite by running: cpanm Mite::Maker --version or perl -MMite::Maker -e 'print $Mite::Maker::VERSION'
- Upgrade Mite to version 0.013000 or later using your Perl package manager
- If using cpanm: run 'cpanm Mite::Maker' or 'cpanm Mite::[email protected]'
- If using cpan: run 'install Mite::Maker'
- If using a system package manager (e.g., apt, yum, pacman), check if an updated package is available
- For distributions containing code generated by Mite, rebuild or regenerate the code after upgrading Mite
- Verify the upgrade was successful by checking the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30672 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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