CVE-2025-54944
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 unrestricted upload of file with dangerous type vulnerability in SUNNET Corporate Training Management System before 10.11 allows remote attackers to write malicious code in a specific file, which may lead to arbitrary code execution.
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 confidenceUnrestricted file upload vulnerability in SUNNET Corporate Training Management System versions prior to 10.11 allows remote attackers to upload files with dangerous types (likely web shells or executable code) to a specific file location, leading to arbitrary code execution on the affected server.
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 versionLocate the version number of the SUNNET Corporate Training Management System (Sun.net Ehrd Ctms) in the application interface, configuration files, or by inspecting HTTP headers/responses. Common locations include the login page footer, admin dashboard, or version.info file in the web root.Affected if The installed version is any release before 10.11 (e.g., 10.10, 10.9, etc.)
-
Verify file upload functionality is enabledAttempt to access the file upload endpoint without authentication. Common paths include /upload, /file/upload, /documents/upload, or similar paths under the CTMS web interface. Check if the upload form or API accepts POST requests.Affected if The file upload feature is accessible without authentication and accepts file submissions.
-
Inspect upload directory locationAfter uploading a harmless test file (e.g., a plain text file), determine the storage path by accessing the file or reviewing application configuration. Check if the upload directory resides inside the web root (e.g., /webapp/uploads/) or outside of it.Affected if Uploaded files are stored within the web-accessible directory tree.
-
Check for script execution restrictions in upload directoryInspect the configuration of the upload directory for restrictions on executable file types. Look for .htaccess rules, web.xml configurations, or equivalent web server settings that block script execution (e.g., .php, .jsp, .asp, .exe files).Affected if No configuration exists to prevent script execution in the upload directory, or script file types are explicitly allowed.
The environment is affected if the installed version is before 10.11 AND the file upload feature is accessible without authentication and stores files in a web-accessible location without script execution restrictions.
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.
dbcve · scoped10.11
Upgrade to SUNNET Corporate Training Management System version 10.11 or later which contains the security fix. If immediate upgrade is not possible, disable file upload functionality or implement strict whitelist-based file type validation and sanitize file paths at the application layer.
10.11
- 1. Create a complete backup of the current Ehrd Ctms database and configuration files
- 2. Download the SUNNET Corporate Training Management System version 10.11 from the official vendor
- 3. Review the vendor's upgrade documentation for version 10.11
- 4. Stop the Ehrd Ctms service before performing the upgrade
- 5. Install version 10.11 following the standard upgrade procedure
- 6. Restart the Ehrd Ctms service after successful installation
- 7. Verify the version upgrade was completed correctly by checking the system information
- 8. Test that file upload functionality works as expected with proper file type restrictions in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54944 — 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-54944 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