CVE-2025-54945
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 · uneditedAn external control of file name or path vulnerability in SUNNET Corporate Training Management System before 10.11 allows remote attackers to execute arbitrary system commands via a malicious file by controlling the destination file path.
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 SUNNET Corporate Training Management System versions prior to 10.11 allows remote attackers to control destination file paths during file operations, enabling arbitrary system command execution through placement of malicious files in web-accessible directories.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.11CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed version of SUNNET Corporate Training Management SystemLocate the application version through the web interface (typically in About/Help sections, footer, or admin panel) or check version files in the application installation directoryAffected if Version is lower than 10.11 (any version prior to 10.11)
-
Verify if web-facing file operation features are accessibleCheck if the application web interface is exposed and accessible externally. Review authentication settings and network exposure of the SUNNET CTMS portalAffected if The web application is accessible without proper access controls or is internet-facing
-
Inspect web-accessible directories for unauthorized filesExamine directories where the application writes or serves files (common locations include upload, temp, public, or root web folders). Look for unexpected files with suspicious extensions (.php, .asp, .jsp, .exe, .sh)Affected if Any suspicious executable or script files exist in web-accessible directories that were not intentionally placed there
-
Review file operation logs for path traversal patternsSearch application and web server logs for unusual path patterns in file operation requests. Look for sequences like '../', '..\', or absolute paths in upload/transfer parametersAffected if Logs contain requests with directory traversal characters in file path parameters
The environment is affected if the installed SUNNET Corporate Training Management System version is prior to 10.11 and the web interface with file operation capabilities is accessible.
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 data10.11
Upgrade to version 10.11 or later; implement strict input validation and path sanitization on all file path parameters to prevent directory traversal characters and ensure files are written only to intended directories.
- 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-54945 — 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-54945 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