dbcve.org
NiagaraApplication · Tridium

CVE-2025-3943

HIGH · 7.5 CVSS v3.1 Published 2025-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Use of GET Request Method With Sensitive Query Strings vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Parameter Injection. This issue affects Niagara Framework: before 4.14.2, before 4.15.1, before 4.10.11; Niagara Enterprise Security: before 4.14.2, before 4.15.1, before 4.10.11. Tridium recommends upgrading to Niagara Framework and Enterprise Security versions 4.14.2u2, 4.15.u1, or 4.10u.11.

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

The Niagara Framework and Enterprise Security products transmit sensitive information (such as authentication tokens, credentials, or session identifiers) as query string parameters in GET HTTP requests. Since GET request URLs are logged by web servers, proxies, browsers, and network monitoring tools, this exposes sensitive data to unauthorized viewers via log files.

MitigationUpgrade Niagara Framework and Niagara Enterprise Security to the recommended versions (4.14.2u2, 4.15.u1, or 4.10u.11) as specified by Tridium. Consider migrating sensitive operations to POST requests or encrypting query parameters as a defense-in-depth measure.

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
NiagaraApplication
Affected:= 4.10u10= 4.14u1= 4.15
Niagara Enterprise SecurityApplication
Affected:= 4.10u10= 4.14u1= 4.15

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed Niagara version
    Check the Niagara installation directory for version information. Typically found in the 'niagara_home' folder, in a 'README.txt', 'release.txt', or by checking the 'version' property in the 'niagara.conf' configuration file. Alternatively, access the Niagara Workbench and navigate to Help > About Niagara to view the exact version.
    Affected if The installed version is 4.10u10 or earlier, 4.14u1, or 4.15 (prior to the fixed releases 4.14.2u2, 4.15.u1, or 4.10u.11).
  2. Identify installed Niagara Enterprise Security version
    If using Niagara Enterprise Security, check the installation for the Enterprise Security module version. This can typically be found in the 'nre' or 'nes' installation folder, or by examining the modules loaded in Niagara Workbench under 'Runtime > Modules'.
    Affected if The Enterprise Security version matches the same affected ranges as the base Niagara platform.
  3. Review web server access logs for sensitive query parameters
    Examine web server logs (such as Apache HTTP server access.log, IIS logs, or Niagara's built-in server logs) for GET requests containing sensitive-looking parameters. Look for patterns like 'token=', 'sessionid=', 'password=', 'credential=', 'auth=', or similar keywords in URL query strings.
    Affected if GET requests contain authentication tokens, session identifiers, or credentials as URL query string parameters in the logs.
  4. Inspect browser developer tools or network traces
    Use browser developer tools (Network tab) or a network proxy to capture live HTTP traffic from the Niagara station. Attempt to log in or access authenticated resources and observe whether sensitive data appears in the URL as query parameters rather than in POST body or headers.
    Affected if Authentication or session-related data is transmitted via GET request query strings instead of POST request bodies or secure headers.

You are affected if your installed Niagara or Niagara Enterprise Security version falls within the affected ranges AND you observe sensitive authentication data being transmitted as query string parameters in GET requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Niagara Framework and Niagara Enterprise Security to the recommended versions (4.14.2u2, 4.15.u1, or 4.10u.11) as specified by Tridium. Consider migrating sensitive operations to POST requests or encrypting query parameters as a defense-in-depth measure.

Recommended fix High confidence

Upgrade to 4.10u.11 (or later 4.10.x), 4.14.2u2 (or later 4.14.x), or 4.15.u1 (or later 4.15.x) depending on your current major version line

  1. 1. Identify the currently installed Niagara Framework or Niagara Enterprise Security version (4.10u10, 4.14u1, or 4.15).
  2. 2. Based on your current major version line, plan the upgrade path: if on 4.10.x upgrade to 4.10u.11 or later; if on 4.14.x upgrade to 4.14.2u2 or later; if on 4.15.x upgrade to 4.15.u1 or later.
  3. 3. Before upgrading, review the Niagara release notes for the target version to understand any prerequisite steps.
  4. 4. Backup the Niagara station and configuration data according to standard backup procedures.
  5. 5. Download the appropriate patched Niagara installation package from the official Tridium/Honeywell download portal.
  6. 6. Apply the upgrade following Tridium's standard upgrade procedures for the Niagara Framework.
  7. 7. After upgrade, verify the version number reflects the patched release.
  8. 8. Test critical functionality to ensure the upgrade did not introduce issues.
Caveat Review release notes for the target version; major version upgrades may introduce breaking changes in custom modules or integrations

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

Fix this in Niagara Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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