CVE-2019-6187: A stored CSV Injection vulnerability was reported in Lenovo XClarity Controller (XCC) that could allow an administrative or other appropriat
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.85% (FIRST EPSS); higher than 58.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A stored CSV Injection vulnerability was reported in Lenovo XClarity Controller (XCC) that could allow an administrative or other appropriately permissioned user to store malformed data in certain XCC server informational fields, that could result in crafted formulas being stored in an exported CSV file. The crafted formula is not executed on XCC itself and has no effect on the server.
- Published
- Nov 19, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 58th percentile
- CWE
- CWE-1236
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| lenovo | xclarity controller | cpe:2.3:a:lenovo:xclarity_controller |
| lenovo | thinkagile 7x82 | cpe:2.3:h:lenovo:thinkagile_7x82 |
| lenovo | thinkagile 7y11 | cpe:2.3:h:lenovo:thinkagile_7y11 |
| lenovo | thinkagile 7y12 | cpe:2.3:h:lenovo:thinkagile_7y12 |
| lenovo | thinkagile 7y88 | cpe:2.3:h:lenovo:thinkagile_7y88 |
| lenovo | thinkagile 7y92 | cpe:2.3:h:lenovo:thinkagile_7y92 |
| lenovo | thinkagile 7z03 | cpe:2.3:h:lenovo:thinkagile_7z03 |
| lenovo | thinksystem sd530 | cpe:2.3:h:lenovo:thinksystem_sd530 |
| lenovo | thinksystem sd650 | cpe:2.3:h:lenovo:thinksystem_sd650 |
| lenovo | thinksystem sn550 | cpe:2.3:h:lenovo:thinksystem_sn550 |
| lenovo | thinksystem sn850 | cpe:2.3:h:lenovo:thinksystem_sn850 |
| lenovo | thinksystem sr150 | cpe:2.3:h:lenovo:thinksystem_sr150 |
and 30 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo xclarity controllerbefore tei392m
- lenovo xclarity controllerbefore cdi340m
- lenovo xclarity controllerbefore g1i312
- lenovo xclarity controllerbefore psi328m
Versions reported by the vendor
Affected version ranges reported by the assigning authority (lenovo). Independent of NVD's CPE analysis and usually ahead of it.
Lenovo Lenovo XClarity Controller (XCC)
- unspecified and later · before TEI392Maffected
- unspecified and later · before CDI340Maffected
- unspecified and later · before G1I312affected
- unspecified and later · before PSI328Maffected
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-38512A privilege escalation vulnerability was discovered in XCC that could allow an authenticated XCC user with elevated privileges to perform co28Monitor
- CVE-2024-38511A privilege escalation vulnerability was discovered in an upload processing functionality of XCC that could allow an authenticated XCC user 28Monitor
- CVE-2024-38510A privilege escalation vulnerability was discovered in the SSH captive command shell interface that could allow an authenticated XCC user wi28Monitor
Published before and after this one in the same product
- Later →CVE-2019-6195Feb 14, 2020 · An authorization bypass exists in Lenovo XClarity Controller (XCC) versions prior to 3.08 CDI340V, 3.01 TEI392O, 1.71 PSI328N where a valid 19Monitor
- Later →CVE-2021-3473Apr 13, 2021 · An internal product security audit of Lenovo XClarity Controller (XCC) discovered that the XCC configuration backup/restore password may be 19Monitor
- Later →CVE-2021-3956May 18, 2022 · A read-only authentication bypass vulnerability was reported in the Third Quarter 2021 release of Lenovo XClarity Controller (XCC) firmware 21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-1236 · Improper Neutralization of Formula Elements in a CSV FileCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.