dbcve.org
On Prem Enterprise ServerApplication · Altium

CVE-2025-27378

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 7.0.6 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
AES contains a SQL injection vulnerability due to an inactive configuration that prevents the latest SQL parsing logic from being applied. When this configuration is not enabled, crafted input may be improperly handled, allowing attackers to inject and execute arbitrary SQL queries.

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

AES contains a SQL injection vulnerability stemming from an inactive configuration that prevents the latest SQL parsing logic from being applied. When this configuration is not enabled, the application fails to properly handle crafted input, allowing attackers to inject and execute arbitrary SQL queries.

MitigationEnable the configuration that activates the latest SQL parsing logic to ensure proper input handling and prevent SQL injection attacks.

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
On Prem Enterprise ServerApplication
Affected:>= 7.0.3, < 7.0.6

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 Altium On Prem Enterprise Server installation
    Locate the Altium On Prem Enterprise Server installation directory or check installed programs list to confirm the product is present
    Affected if Altium On Prem Enterprise Server is not installed on the system
  2. Check installed version
    Use the product's version information utility or check the version file in the installation directory to determine the exact version number
    Affected if Version is >= 7.0.3 and < 7.0.6
  3. Locate SQL parsing configuration
    Examine the application configuration files (such as config files in the installation directory or configuration subfolder) for settings related to SQL parsing logic
    Affected if A configuration option controlling SQL parsing logic exists but cannot be located or read
  4. Verify SQL parsing configuration status
    Inspect the configuration file to determine whether the setting that activates the latest SQL parsing logic is disabled or not explicitly enabled
    Affected if The configuration that enables the latest SQL parsing logic is disabled or absent, leaving the legacy parsing logic active

The environment is affected if Altium On Prem Enterprise Server version 7.0.3 through 7.0.6 is installed AND the configuration that activates the latest SQL parsing logic is disabled or not enabled.

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.

dbcve · scoped
Upgrade available Upgrade to 7.0.6 or later
Fixed in 7.0.6
Interim mitigation

Enable the configuration that activates the latest SQL parsing logic to ensure proper input handling and prevent SQL injection attacks.

Recommended fix High confidence

Altium Enterprise Server 7.0.6 or later

  1. 1. Identify all Altium Enterprise Server instances running version 7.0.3, 7.0.4, or 7.0.5
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Backup the existing database and configuration files
  4. 4. Download Altium Enterprise Server version 7.0.6 or later from the official Altium portal at www.altium.com
  5. 5. Stop all Enterprise Server services
  6. 6. Run the installer/upgrader to update to version 7.0.6 or latest stable release
  7. 7. Verify the SQL parsing configuration is properly enabled after upgrade (consult Altium documentation for post-upgrade configuration verification)
  8. 8. Restart all Enterprise Server services
Caveat Review Altium release notes for version 7.0.6 for any changes to functionality, API, or workflow that may affect existing integrations or custom configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in On Prem Enterprise Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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