CVE-2025-30596
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in tstafford include-file include-file allows Path Traversal.This issue affects include-file: from n/a through <= 1.
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 · moderate confidenceThe include-file component from tstafford contains a path traversal vulnerability that allows attackers to access files outside the intended restricted directory through specially crafted file paths containing '../' sequences in the include functionality.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Locate the include-file component from tstaffordSearch for files or packages named 'include-file', 'tstafford', or related include functionality in your application directories and dependency manifests (e.g., package.json, requirements.txt, Gemfile, or similar).Affected if The component is present in your environment
-
Identify the installed versionCheck the version metadata in the component's package definition, README, or version file if present. Compare against any known version ranges provided in CVE databases or security advisories.Affected if The installed version falls within the affected range or cannot be determined (treat as potentially affected)
-
Determine if include functionality processes external inputReview the include-file component's source code or configuration to identify whether user-supplied file paths, parameters, or request inputs are passed to the include functionality.Affected if External input is passed to the include feature without apparent validation
-
Inspect path handling for traversal sequencesSearch the component's code for file path processing logic. Look for whether '../' sequences or similar path traversal patterns are filtered, sanitized, or validated before being used to access files.Affected if Path traversal sequences are not explicitly blocked or canonicalized paths are not validated to stay within allowed directories
-
Check if the component exposes file inclusion over the networkIdentify whether the include functionality is accessible via web requests, APIs, or any network-facing interface that could accept malicious path inputs from attackers.Affected if The include functionality is network-accessible and accepts path parameters
Your environment is affected if the tstafford include-file component is present, accepts external path input, and lacks proper path traversal validation to restrict file access to the intended directory.
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.
From vendor dataImplement strict path validation with canonicalization checks to ensure resolved file paths remain within the intended directory, rejecting any input containing directory traversal sequences.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30596 — 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-30596 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