CVE-2023-25341
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 · uneditedA Directory Traversal vulnerability in ladle dev server 2.5.1 and earlier allows an attacker on the same network to read files accessible to the user via GET requests.
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 confidenceA Directory Traversal vulnerability in ladle dev server versions 2.5.1 and earlier allows an attacker on the same network to craft malicious GET requests with path traversal sequences (e.g., ../../) to access and read files outside the intended web root directory that are accessible to the user running the server.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/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.
-
Check if ladle is installed in the projectInspect the project's package.json file for ladle in the dependencies or devDependencies section. Alternatively, run 'npm list ladle' or 'yarn list ladle' to list the installed package.Affected if ladle is listed as a dependency in package.json or is present in node_modules
-
Determine the installed ladle versionRun 'npm list ladle' or 'yarn list ladle' to display the installed version. Check package-lock.json or yarn.lock for the resolved version as well.Affected if The installed version is 2.5.1 or any version lower than 2.5.1
-
Verify if the dev server could be network-accessibleCheck the package.json scripts section for the 'dev' or 'serve' command. Inspect any ladle.config.js or vite.config.js files for host configuration. Look for '--host' flag or 'host: true' which exposes the server to non-localhost interfaces.Affected if The dev server is configured to listen on all network interfaces (0.0.0.0) or explicitly uses the --host flag, allowing remote access
-
Confirm the dev server is actively used or was recently usedReview recent git commits, CI/CD pipelines, or developer workflows that invoke 'ladle dev' or 'ladle serve'. Check for any exposed endpoints in development environment logs or documentation.Affected if The ladle dev server is being run in a shared or networked development environment
You are affected if ladle version 2.5.1 or earlier is installed AND the dev server is exposed to network access beyond localhost.
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 dataUpgrade ladle to the latest version beyond 2.5.1 which should contain the path traversal fix; if no patched version is available, avoid exposing the dev server to untrusted networks or disable it in production environments.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25341 — 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-2023-25341 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