dbcve.org
PcvueApplication · Arcinfo

CVE-2026-1698

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 16.3.4 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
A HTTP Host header attack vulnerability affects WebClient and the WebScheduler web apps of PcVue in version 15.0.0 through 16.3.3 included, allowing a remote attacker to inject harmful payloads that manipulate server-side behavior. This vulnerability only affects the endpoints /Authentication/ExternalLogin, /Authentication/AuthorizationCodeCallback and /Authentication/Logout of the WebClient and WebScheduler web apps.

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 · moderate confidence

HTTP Host header injection vulnerability in PcVue's WebClient and WebScheduler web applications (versions 15.0.0-16.3.3) allows remote attackers to inject malicious payloads via the Host header, affecting the /Authentication/ExternalLogin, /Authentication/AuthorizationCodeCallback, and /Authentication/Logout endpoints. This can manipulate server-side behavior for authentication-related operations.

MitigationUpgrade PcVue to version 16.3.4 or later to obtain the vendor patch; alternatively, implement a web application firewall (WAF) or reverse proxy to validate and reject malformed Host headers before they reach the application.

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
PcvueApplication
Affected:>= 15.0.0, <= 15.2.13>= 16.0.0, < 16.3.4

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. Confirm PcVue installation and version
    Locate the installed PcVue software and determine its version number. Check the application directory, registry entries, or the About dialog within PcVue. Compare the version against the affected ranges: 15.0.0-15.2.13 or 16.0.0-16.3.3
    Affected if The installed version falls within 15.0.0 through 15.2.13, or 16.0.0 through 16.3.3
  2. Verify WebClient or WebScheduler are deployed
    Check if the PcVue WebClient or WebScheduler web applications are installed and running. Inspect the web server (IIS) configuration or application directory for these web components
    Affected if WebClient or WebScheduler web applications are present on the server
  3. Check if authentication endpoints are exposed
    Inspect the web server to confirm the /Authentication/ExternalLogin, /Authentication/AuthorizationCodeCallback, and /Authentication/Logout endpoints are accessible
    Affected if Any of the three affected endpoints are publicly or internally accessible
  4. Determine if external authentication is in use
    Review the web application configuration files or authentication settings to check if external login providers (such as OAuth or SAML) are configured for the web client
    Affected if External authentication providers are enabled or configured for the application

A user is affected if PcVue version is between 15.0.0-15.2.13 or 16.0.0-16.3.3 AND the WebClient or WebScheduler web components are running with accessible authentication endpoints.

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 16.3.4 or later
Fixed in 16.3.4
Interim mitigation

Upgrade PcVue to version 16.3.4 or later to obtain the vendor patch; alternatively, implement a web application firewall (WAF) or reverse proxy to validate and reject malformed Host headers before they reach the application.

Recommended fix Moderate confidence

PcVue 16.3.4 or later (for version 16.x line); for version 15.x, upgrade to the 16.x line at 16.3.4 or later

  1. Identify the currently installed PcVue version by checking the application or system information
  2. Download PcVue version 16.3.4 or later from the official vendor website (www.pcvue.com)
  3. Backup the current PcVue installation and configuration files before upgrading
  4. Install the upgraded version (16.3.4 or later) following the vendor's standard upgrade procedure
  5. Verify that the WebClient and WebScheduler applications are functioning correctly after upgrade
  6. Test the affected endpoints (/Authentication/ExternalLogin, /Authentication/AuthorizationCodeCallback, /Authentication/Logout) to confirm the vulnerability is remediated
Caveat Upgrading from version 15.x to 16.x may introduce compatibility changes; review vendor release notes for breaking changes between these major version lines

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

Fix this in Pcvue Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1698 — 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-2026-1698 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