CVE-2026-7490
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 and CPAS developed by Sunnet has an Arbitrary File Upload vulnerability, allowing privileged remote attackers to upload and execute web shell backdoors, thereby enabling arbitrary code execution on the server.
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 · high confidenceArbitrary file upload vulnerability in Sunnet's CTMS and CPAS allows authenticated privileged attackers to upload malicious files (web shells) to the server, achieving arbitrary code execution.
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 versionsall 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 Sunnet product installationInventory your web applications and servers to identify if Sun.net Ehrd Cpas or Sun.net Ehrd Ctms is deployed. Check installed software lists, application directories, or consult your system documentation.Affected if Either Sun.net Ehrd Cpas or Sun.net Ehrd Ctms is present in the environment.
-
Locate file upload functionalitySearch the application's web interface for file upload features, typically found in user profile settings, document management sections, or administrative panels. Identify the upload endpoint URLs and associated form fields.Affected if The application provides a file upload feature accessible to authenticated privileged users.
-
Verify upload storage locationExamine the application configuration or server settings to determine where uploaded files are stored. Check if files are saved within the web root (htdocs, www, public_html) or outside the web-accessible directory tree.Affected if Uploaded files are stored within the web root directory, making them directly accessible via HTTP requests.
-
Check script execution settingsReview web server configuration (Apache .htaccess, IIS handler mappings, or equivalent) for the upload directory. Determine if script execution permissions are disabled or if the server is configured to prevent execution of uploaded file types.Affected if The upload directory allows script execution (PHP, JSP, ASP, etc.) or has no restrictions preventing uploaded scripts from running.
If Sun.net Ehrd Cpas or Ctms is installed and the upload feature is accessible to authenticated privileged users with files stored in the web root without script execution restrictions, the environment is affected by this 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 dataImplement strict server-side file type validation, store uploaded files outside the web root, disable script execution in upload directories, and apply principle of least privilege to upload functionality.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7490 — 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-7490 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