Concert
by IBM
CVEs (95)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-36158 | Med | 0.33 | 5.1 | 0.00 | Nov 20, 2025 | IBM Concert 1.0.0 through 2.0.0 could allow a local user with specific permission to obtain sensitive information from files due to uncontrolled recursive directory copying. | ||
| CVE-2026-6327 | Med | 0.28 | 4.3 | 0.00 | Sep 23, 2026 | IBM Concert 1.0.0 through 3.0.0 could allow an unauthorized user to inject data into log messages due to improper neutralization of special elements when written to log files. | ||
| CVE-2024-52359 | Med | 0.28 | 4.3 | 0.00 | Nov 19, 2024 | IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 could allow an authenticated user to perform unauthorized actions that should be reserved to administrator used due to improper access controls. | ||
| CVE-2024-37070 | Med | 0.28 | 4.3 | 0.00 | Nov 19, 2024 | IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 could allow an authenticated user to obtain sensitive information that could aid in further attacks against the system. | ||
| CVE-2024-43180 | Med | 0.28 | 4.3 | 0.00 | Sep 13, 2024 | IBM Concert 1.0 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and… | ||
| CVE-2026-3628 | Med | 0.27 | 5.3 | 0.00 | Oct 19, 2026 | IBM Concert 1.0 through 3.0.0 allows information disclosure through exposure of schema suggestions. | ||
| CVE-2026-15661 | Med | 0.27 | 5.3 | 0.00 | Oct 19, 2026 | IBM Concert 1.0 through 3.0.0 could allow an unauthorized user to inject data into log messages due to improper neutralization of special elements when written to log files. | ||
| CVE-2026-1510 | Med | 0.24 | 4.7 | 0.00 | Oct 19, 2026 | IBM Concert 1.0 through 3.0.0 is vulnerable to Information Disclosure via Heap Inspection. | ||
| CVE-2024-49827 | Low | 0.24 | 3.7 | 0.00 | Aug 18, 2025 | IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to excessive data exposure, allowing attackers to access sensitive information without proper filtering. | ||
| CVE-2024-43173 | Low | 0.24 | 3.7 | 0.00 | Oct 22, 2024 | IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute. | ||
| CVE-2025-33081 | Low | 0.21 | 3.3 | 0.00 | Feb 3, 2026 | IBM Concert 1.0.0 through 2.1.0 stores potentially sensitive information in log files that could be read by a local user. | ||
| CVE-2026-4405 | Med | 0.19 | 4.0 | 0.00 | Oct 19, 2026 | IBM Concert 1.0 through 3.0.0 allows web page cache to be stored locally which can be read by another user on the system. | ||
| CVE-2026-3303 | Low | 0.17 | 3.7 | 0.00 | Oct 19, 2026 | IBM Concert 1.0 through 3.0.0 uses cross-origin resource sharing (CORS) which could allow an attacker to carry out privileged actions as the domain name is not being limited to only trusted domains. | ||
| CVE-2026-1501 | Low | 0.17 | 3.7 | 0.00 | Oct 19, 2026 | IBM Concert 1.0 through 3.0.0 is vulnerable to Improper Certificate Validation. | ||
| CVE-2026-6930 | Low | 0.17 | 3.7 | 0.00 | Oct 19, 2026 | IBM Concert 1.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. |
- risk 0.33cvss 5.1epss 0.00
IBM Concert 1.0.0 through 2.0.0 could allow a local user with specific permission to obtain sensitive information from files due to uncontrolled recursive directory copying.
- risk 0.28cvss 4.3epss 0.00
IBM Concert 1.0.0 through 3.0.0 could allow an unauthorized user to inject data into log messages due to improper neutralization of special elements when written to log files.
- risk 0.28cvss 4.3epss 0.00
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 could allow an authenticated user to perform unauthorized actions that should be reserved to administrator used due to improper access controls.
- risk 0.28cvss 4.3epss 0.00
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 could allow an authenticated user to obtain sensitive information that could aid in further attacks against the system.
- risk 0.28cvss 4.3epss 0.00
IBM Concert 1.0 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and…
- risk 0.27cvss 5.3epss 0.00
IBM Concert 1.0 through 3.0.0 allows information disclosure through exposure of schema suggestions.
- risk 0.27cvss 5.3epss 0.00
IBM Concert 1.0 through 3.0.0 could allow an unauthorized user to inject data into log messages due to improper neutralization of special elements when written to log files.
- risk 0.24cvss 4.7epss 0.00
IBM Concert 1.0 through 3.0.0 is vulnerable to Information Disclosure via Heap Inspection.
- risk 0.24cvss 3.7epss 0.00
IBM Concert Software 1.0.0 through 1.1.0 is vulnerable to excessive data exposure, allowing attackers to access sensitive information without proper filtering.
- risk 0.24cvss 3.7epss 0.00
IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute.
- risk 0.21cvss 3.3epss 0.00
IBM Concert 1.0.0 through 2.1.0 stores potentially sensitive information in log files that could be read by a local user.
- risk 0.19cvss 4.0epss 0.00
IBM Concert 1.0 through 3.0.0 allows web page cache to be stored locally which can be read by another user on the system.
- risk 0.17cvss 3.7epss 0.00
IBM Concert 1.0 through 3.0.0 uses cross-origin resource sharing (CORS) which could allow an attacker to carry out privileged actions as the domain name is not being limited to only trusted domains.
- risk 0.17cvss 3.7epss 0.00
IBM Concert 1.0 through 3.0.0 is vulnerable to Improper Certificate Validation.
- risk 0.17cvss 3.7epss 0.00
IBM Concert 1.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
Page 5 of 5