CVE-2025-41428
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') issue exists in TimeWorks 10.0 to 10.3. If exploited, arbitrary JSON files on the server may be viewed by a remote unauthenticated attacker.
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 confidencePath traversal vulnerability in TimeWorks versions 10.0-10.3 allows remote unauthenticated attackers to read arbitrary JSON files on the server by manipulating file path inputs.
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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm TimeWorks installationLocate the TimeWorks application on the system. Check for the software in installed programs (Windows: Control Panel > Programs and Features, Linux: dpkg -l or rpm -qa), or identify the web service running on the server.Affected if TimeWorks software is installed on the system
-
Check TimeWorks versionAccess the TimeWorks admin interface or use the application's built-in version check (typically found in Help > About, or query the API endpoint /api/version). Compare the installed version against the affected range 10.0-10.3.Affected if The installed version falls within 10.0 through 10.3 inclusive
-
Identify file path input functionalityExamine the TimeWorks web interface or API for endpoints or parameters that accept file paths, particularly those related to JSON file loading, configuration imports, or file preview features.Affected if A feature accepting file path input is accessible (even without authentication)
-
Test for path traversal exposureIf a file path input is found, attempt to access a known JSON file outside the expected directory using traversal sequences such as ../../../../../../etc/passwd or similar paths. On Windows, try ..\..\..\windows\win.ini. Observe if the application returns file contents.Affected if The application returns contents of files outside the intended directory, confirming the path traversal is exploitable
The system is affected if TimeWorks version 10.0-10.3 is running and a file path input feature is accessible, allowing unauthenticated users to read arbitrary JSON files via path traversal sequences.
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 path sanitization to restrict file access, and upgrade to a patched version once available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41428 — 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-41428 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