CVE-2026-7489
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 · uneditedCTMS developed by Sunnet has a SQL Injection vulnerability, allowing authenticated remote attackers to inject arbitrary SQL commands to read, modify, and delete database contents.
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 confidenceSunnet's CTMS contains a SQL injection vulnerability that allows authenticated remote attackers to inject arbitrary SQL commands. This can lead to unauthorized read, modification, or deletion of sensitive clinical trial data in the database.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Sun.net Ehrd Ctms is installedCheck for the CTMS application directory, web server configuration files, or running services matching 'ctms', 'ehrd', or 'sunnet'. Inspect system services, installed applications list, or web server document roots for CTMS components.Affected if The Sun.net Ehrd Ctms application is found running or installed on the system
-
Verify web interface accessibilityIdentify exposed HTTP/HTTPS endpoints for the CTMS application by reviewing web server configs, reverse proxy settings, or network listener configurations. Attempt to access the login or main portal page.Affected if The CTMS web interface is accessible over the network
-
Identify authentication mechanismReview CTMS configuration files (typically in conf/, config/, or settings directories) for authentication settings. Check whether the application uses form-based login, API keys, session tokens, or database-backed credentials.Affected if The application uses database-authenticated accounts for user login
-
Inspect database query implementationExamine application source code files (especially in modules handling user input such as login, search, or data retrieval) for direct string concatenation in SQL queries versus parameterized queries or prepared statements. Look for patterns like 'SELECT * FROM' + variable or 'WHERE ' + user_input.Affected if Dynamic SQL queries are constructed using string concatenation with user-supplied input without parameterized queries
-
Check database for suspicious activityReview database transaction logs, audit logs, or query logs for unusual SQL patterns such as UNION SELECT, OR 1=1, DROP TABLE, or multiple statements separated by semicolons originating from CTMS application connections.Affected if Database logs show SQL injection attempts or unusual query patterns from CTMS user sessions
If Sun.net Ehrd Ctms is installed with its web interface exposed and uses database-authenticated accounts with dynamic SQL queries handling user input, the environment is likely affected by this SQL injection vulnerability.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements across the application, apply principle of least privilege to database accounts, and validate all user inputs before database queries.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7489 — 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-2026-7489 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