CVE-2025-3943 json
Use of GET Request Method With sensitive Query Strings
published last yr. modified 4mo ago also EUVD-2025-16142
- cvss
- 4.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.4%
- EPSS 11.4% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Tridium Niagara Framework 4.10.11, 4.14.2, 4.15.1
- Tridium Niagara Enterprise Security 4.10.11, 4.14.2, 4.15.1
Is CVE-2025-3943 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
11.38% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Tridium Niagara Framework
- Tridium Niagara Enterprise Security
Classification
- Weakness
-
- CWE-598 Use of HTTP Request With Sensitive Query String
References
-
honeywell.com
/us/en/product-security#security-notices
vendor-advisory
-
docs.niagara-community.com
/category/tech_bull
vendor-advisory, permissions-required
Sources
- CVE List CVE-2025-3943
- NVD CVE-2025-3943
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.