CVE-2026-3627
published 2026-08-28CVE-2026-3627: IBM Concert 1.0.0 through 2.3.1 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker…
PriorityP359critical9.1CVSS 3.1
AVNACLPRNUINSUCHIHAN
EPSS
0.51%
42.8th percentile
IBM Concert 1.0.0 through 2.3.1 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| ibm | concert | 1.0.0 – 2.3.1 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
IBM Concert 1.0.0 through 2.3.1 is vulnerable to SQL injection.
ghsa_unreviewed·2026-08-29
CVE-2026-3627 [CRITICAL] IBM Concert 1.0.0 through 2.3.1 is vulnerable to SQL injection.
IBM Concert 1.0.0 through 2.3.1 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
VulDB
IBM Concert up to 2.3.1 sql injection
vuldb·2026-08-29·CVSS 9.1
CVE-2026-3627 [CRITICAL] IBM Concert up to 2.3.1 sql injection
A vulnerability described as critical has been identified in IBM Concert up to 2.3.1. This affects an unknown part. Such manipulation leads to sql injection.
This vulnerability is documented as CVE-2026-3627. The attack can be executed remotely. There is not any exploit available.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-08-28
Published