dbcve.org
Conprosys Hmi SystemApplication · Contec

CVE-2025-34080

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-01
Fix available
A fix is available. Upgrade to 3.7.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The Contec Co.,Ltd. CONPROSYS HMI System (CHS) is vulnerable to Cross-Site Scripting (XSS) in the getqsetting.php functionality that could allow reflected execution of scripts in the browser on interaction.This issue affects CONPROSYS HMI System (CHS): before 3.7.7.

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 confidence

Reflected XSS vulnerability in the getqsetting.php file of CONPROSYS HMI System (CHS) allows attackers to inject malicious scripts that execute in a victim's browser when they interact with a crafted link. This affects versions prior to 3.7.7.

MitigationUpdate CONPROSYS HMI System to version 3.7.7 or later. Until patched, implement input validation on the getqsetting.php endpoint and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

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
Conprosys Hmi SystemApplication
Affected:< 3.7.7

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if CONPROSYS HMI System is installed
    Check for CHS installation directories, running services, or look for the web application's HTTP responses (often on port 80/443 or custom ports). Search for 'conprosys' or 'CHS' in installed programs and running processes.
    Affected if CONPROSYS HMI System is present on the system
  2. Determine the installed CHS version
    Access the application's About page, check version info in installation directories, review configuration files, or query the application directly for its version identifier.
    Affected if The version is less than 3.7.7 or cannot be determined (treat as vulnerable)
  3. Locate and verify the getqsetting.php file
    Search the web root or application directory for getqsetting.php. Check if it is accessible via HTTP/HTTPS by attempting to access it directly in a browser or via curl.
    Affected if The file exists and is accessible via the web interface
  4. Test for XSS vulnerability in getqsetting.php
    Send a crafted request with a test XSS payload in the query parameters (e.g., ?param=<script>alert(1)</script>) and verify if the payload is reflected back unescaped in the response.
    Affected if The injected script content appears verbatim in the HTTP response without HTML encoding

The environment is affected if CONPROSYS HMI System is installed with a version prior to 3.7.7 and the getqsetting.php endpoint is accessible and reflects user input without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.7.7 or later
Fixed in 3.7.7
Interim mitigation

Update CONPROSYS HMI System to version 3.7.7 or later. Until patched, implement input validation on the getqsetting.php endpoint and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

Conprosys HMI System (CHS) version 3.7.7

  1. 1. Identify the current version of CONPROSYS HMI System (CHS) installed by checking the system documentation or administration interface
  2. 2. Confirm the installed version is below 3.7.7 (any version < 3.7.7 is affected by this XSS vulnerability in getqsetting.php)
  3. 3. Obtain the patched version 3.7.7 or later from the official Contec vendor website or through their support channels
  4. 4. Follow the vendor's documented upgrade procedure to apply version 3.7.7 or later
  5. 5. After upgrading, verify the getqsetting.php functionality no longer reflects unsanitized input and the version displays as 3.7.7 or higher
  6. 6. Test that the XSS vulnerability is resolved by attempting to inject benign script payload in the affected parameter and confirming it is not executed
Caveat Review Contec release notes for 3.7.7 to check for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Conprosys Hmi System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34080 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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