SQL Injection in AES Due to Inactive SQL Parsing Configuration

published 2026-01-22 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-4176

cvss: 8.6; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

Altium AES 7.0.6

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 9 mo ago (2026-01-22)

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.6	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Altium AES

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command
CWE-20 Improper Input Validation

References

altium.com /platform/security-compliance/security-advisories
vendor-advisory

Sources

CVE List CVE-2025-27378
NVD CVE-2025-27378

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary