Ehrd CtmsApplication · Sun.net

CVE-2025-54946

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-30
Fix available
A fix is available. Upgrade to 10.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A SQL injection vulnerability in SUNNET Corporate Training Management System before 10.11 allows remote attackers to execute arbitrary SQL commands.

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 confidence

A critical SQL injection vulnerability exists in SUNNET Corporate Training Management System versions prior to 10.11. The flaw allows remote, unauthenticated attackers to inject and execute arbitrary SQL commands via unsanitized input fields, potentially leading to complete database compromise, data exfiltration, or system takeover.

MitigationUpgrade to version 10.11 or later which contains the security fix. As an interim measure, implement strict input validation and parameterized queries across all database interactions.

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
Ehrd CtmsApplication
Affected:< 10.11

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of SUNNET Corporate Training Management System
    Check the application version displayed in the software UI, system configuration panel, or version file (commonly found in about.php, version.ini, or the application's help/about section)
    Affected if The displayed version number is lower than 10.11 (e.g., 10.10, 10.9, etc.)
  2. Locate the database configuration file
    Examine the application's configuration directory for files containing database connection strings, such as config.php, db_config.xml, or application.properties
    Affected if The configuration file exists and the application connects to a database (SQL injection requires an active database connection to be exploitable)
  3. Identify input fields that accept user data
    Review login forms, search boxes, registration fields, and any parameters that accept user input and interact with the database (check HTTP requests and form handlers)
    Affected if The application has input fields that pass user data directly to SQL queries without visible sanitization or use of parameterized queries
  4. Test for unsanitized SQL input (optional, requires authorization)
    If authorized, submit a single quote (') or common SQL injection payloads (e.g., ' OR '1'='1) into input fields and observe database error responses
    Affected if The application returns SQL syntax errors or behaves unexpectedly, indicating unsanitized input is processed
  5. Verify database user privileges
    Check the database user account used by the application (via configuration files or database admin tools)
    Affected if The application database user has elevated privileges (e.g., db_owner, root) rather than limited read/write permissions

You are affected if your installed SUNNET Corporate Training Management System version is below 10.11 and the application processes user input through database queries without proper sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 10.11 or later
Fixed in 10.11
Interim mitigation

Upgrade to version 10.11 or later which contains the security fix. As an interim measure, implement strict input validation and parameterized queries across all database interactions.

Fix this in Ehrd Ctms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54946 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54946 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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