CVE-2025-31635
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 LambertGroup CLEVER lbg-audio11-html5-shoutcast_history allows Path Traversal.This issue affects CLEVER: from n/a through <= 2.6.
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 confidenceA path traversal vulnerability in the CLEVER lbg-audio11-html5-shoutcast_history component (versions <= 2.6) allows attackers to manipulate file path inputs using '..' sequences to access files outside the web application's restricted directory, potentially exposing sensitive system files.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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.
-
Identify if CLEVER lbg-audio11-html5-shoutcast_history is installedSearch the web server filesystem for directories or files containing 'lbg-audio11-html5-shoutcast_history' or 'shoutcast_history'. Check web application source code for references to this component.Affected if The component directory or files are found on the system
-
Determine the installed version of the shoutcast_history componentLocate any version file, manifest, or configuration that displays the component version. Check the main component directory for a version identifier.Affected if The version is 2.6 or lower
-
Verify the shoutcast_history web component is accessible via HTTP/HTTPSAttempt to access the shoutcast_history endpoint (e.g., /shoutcast_history/ or similar paths) through the web server to confirm it is exposed.Affected if The component responds to HTTP requests and accepts file path parameters
-
Test for path traversal vulnerabilitySend a request with '../' sequences in any file path parameter (e.g., ?file=../../etc/passwd or similar) to the shoutcast_history endpoint and observe if files outside the intended directory are returned.Affected if The application returns content from files outside the designated directory
-
Review web server logs for suspicious path traversal requestsExamine access logs for the shoutcast_history endpoint for patterns containing '..' sequences in the request URL or parameters.Affected if Log entries show attempted or successful path traversal sequences
You are affected if CLEVER lbg-audio11-html5-shoutcast_history version 2.6 or lower is installed and the component is accessible via the web with file path input functionality.
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 input validation and canonicalization of file paths to prevent traversal sequences; restrict file access to intended directories and apply the principle of least privilege.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31635 — 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-31635 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