ILM Informatique OpenConcerto 1.7.5 credentials storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in ILM Informatique OpenConcerto 1.7.5. This affects an unknown function. This manipulation causes credentials storage. This vulnerability appears as CVE-2026-6500. The attack requires local access. There is no available exploit.
Details
A vulnerability classified as problematic was found in ILM Informatique OpenConcerto 1.7.5. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a credentials storage vulnerability. The CWE definition for the vulnerability is CWE-256. Storing a password in plaintext may result in a system compromise. As an impact it is known to affect confidentiality. The summary by CVE is:
Plaintext storage of a password vulnerability in ILM Informatique OpenConcerto allows Retrieve Embedded Sensitive Data. This issue affects OpenConcerto: 1.7.5.
The weakness was presented by Dominique Righetto. The advisory is shared at openconcerto.org. This vulnerability is known as CVE-2026-6500 since 04/17/2026. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Credentials storageCWE: CWE-256 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/17/2026 CVE reserved05/04/2026 Advisory disclosed
05/04/2026 VulDB entry created
05/04/2026 VulDB entry last update
Sources
Advisory: openconcerto.orgResearcher: Dominique Righetto
Status: Confirmed
CVE: CVE-2026-6500 (🔒)
GCVE (CVE): GCVE-0-2026-6500
GCVE (VulDB): GCVE-100-360973
Entry
Created: 05/04/2026 17:45Changes: 05/04/2026 17:45 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.