CVE-2023-29154
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL injection vulnerability exists in the CONPROSYS HMI System (CHS) versions prior to 3.5.3. A user who can access the affected product with an administrative privilege may execute an arbitrary SQL command via specially crafted input to the query setting page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in CONPROSYS HMI System (CHS) versions before 3.5.3 allows authenticated administrators to execute arbitrary SQL commands through specially crafted input in the query setting page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.5.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed CONPROSYS HMI System versionLocate and read the version information from the CHS application interface, configuration files, or system information panel. This is typically found in the About section, system settings, or a version info/config file in the installation directory.Affected if Installed version is any version before 3.5.3
-
Verify access to query setting pageNavigate to or enumerate the query setting page within the CHS administrative interface. Check if this feature is present and accessible in the system.Affected if Query setting page feature exists and is accessible
-
Confirm administrative authentication statusReview user accounts and their privilege levels in the CHS user management section. Determine if any account has administrative privileges that would grant access to the query setting functionality.Affected if Administrative user accounts exist and can access the query setting page
System is affected if CONPROSYS HMI System version is below 3.5.3 and administrative access to the query setting page is available
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.5.3
Upgrade CONPROSYS HMI System to version 3.5.3 or later to address the SQL injection vulnerability. Restrict administrative access and monitor for suspicious queries.
CONPROSYS HMI System (CHS) version 3.5.3
- Verify the current installed version of CONPROSYS HMI System
- Back up all project files, configurations, and databases associated with the current installation
- Download CONPROSYS HMI System version 3.5.3 or later from the official Contec website (www.contec.com)
- Stop any running services or processes related to CONPROSYS HMI System
- Install version 3.5.3 following the vendor's standard upgrade procedures
- Restart the CONPROSYS HMI System services
- Verify the installation was successful and the application functions normally
- Confirm the version number displays as 3.5.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29154 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data