An authenticated XCC user with elevated privileges can perform blind SQL injection in limited cases through a crafted API command.
Noroxi assessment
Priority: Monitor (action score 28/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.40% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 4.1, NVD 7.2.
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
An authenticated XCC user with elevated privileges can perform blind SQL injection in limited cases through a crafted API command. This affects ThinkSystem v2 and v3 servers with XCC; ThinkSystem v1 servers are not affected.
- Published
- Oct 25, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 33th percentile
- CWE
- CWE-89
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.2
- CNA · lenovo
- 4.1
- 3.1 point gap
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 | thinkagile hx5530 firmware | cpe:2.3:o:lenovo:thinkagile_hx5530_firmware |
| lenovo | thinkagile hx5530 | cpe:2.3:h:lenovo:thinkagile_hx5530 |
| lenovo | thinkagile hx7530 firmware | cpe:2.3:o:lenovo:thinkagile_hx7530_firmware |
| lenovo | thinkagile hx7530 | cpe:2.3:h:lenovo:thinkagile_hx7530 |
| lenovo | thinkagile vx3331 firmware | cpe:2.3:o:lenovo:thinkagile_vx3331_firmware |
| lenovo | thinkagile vx3331 | cpe:2.3:h:lenovo:thinkagile_vx3331 |
| lenovo | thinkagile hx1331 firmware | cpe:2.3:o:lenovo:thinkagile_hx1331_firmware |
| lenovo | thinkagile hx1331 | cpe:2.3:h:lenovo:thinkagile_hx1331 |
| lenovo | thinkagile hx2330 firmware | cpe:2.3:o:lenovo:thinkagile_hx2330_firmware |
| lenovo | thinkagile hx2330 | cpe:2.3:h:lenovo:thinkagile_hx2330 |
| lenovo | thinkagile hx2331 firmware | cpe:2.3:o:lenovo:thinkagile_hx2331_firmware |
| lenovo | thinkagile hx2331 | cpe:2.3:h:lenovo:thinkagile_hx2331 |
and 92 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo thinkagile hx1331 firmwareall versions
- lenovo thinkagile hx2330 firmwareall versions
- lenovo thinkagile hx2331 firmwareall versions
- lenovo thinkagile hx3330 firmwareall versions
- lenovo thinkagile hx3331 firmwareall versions
- lenovo thinkagile hx3375 firmwareall versions
- lenovo thinkagile hx3376 firmwareall versions
- lenovo thinkagile hx5530 firmwareall versions
- lenovo thinkagile hx5531 firmwareall versions
- lenovo thinkagile hx7530 firmwareall versions
- lenovo thinkagile hx7531 firmwareall versions
- lenovo thinkagile mx3330-f all-flash firmwareall versions
- lenovo thinkagile mx3330-h hybrid firmwareall versions
- lenovo thinkagile mx3331-f all-flash firmwareall versions
- lenovo thinkagile mx3331-h hybrid firmwareall versions
- lenovo thinkagile mx3530 f all flash firmwareall versions
- lenovo thinkagile mx3530-h hybrid firmwareall versions
- lenovo thinkagile mx3531 h hybrid firmwareall versions
- lenovo thinkagile mx3531-f all-flash firmwareall versions
- lenovo thinkagile vx2330 firmwareall versions
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)
- variousaffected
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4607An authenticated XCC user can change permissions for any user through a crafted API command.35Monitor
- CVE-2023-25492A valid, authenticated user may be able to trigger a denial of service of the XCC web user interface or other undefined behavior through a f35Monitor
- CVE-2023-0683A valid, authenticated XCC user with read only access may gain elevated privileges through a specifically crafted API call.35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-25495Apr 28, 2023 · A valid, authenticated administrative user can query a web interface API to reveal the configured LDAP client password used by XCC to authen19Monitor
- ← EarlierCVE-2023-29056Apr 28, 2023 · A valid LDAP user, under specific conditions, will default to read-only permissions when authenticating into XCC.23Monitor
- ← EarlierCVE-2023-4606Oct 25, 2023 · An authenticated XCC user with Read-Only permission can change a different user’s password through a crafted API command.32Monitor
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.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
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.