Skip to main content

Johnson Controls EUVDEUVD-2026-91067

| CVE-2026-71454 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-01 jci GHSA-3rxj-9m49-463x
5.8
CVSS 4.0 · Vendor: jci
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege user
  2. Delivery
    Inject crafted XSS payload into input field
  3. Exploit
    Payload stored/reflected in generated page
  4. Execution
    Victim renders page, script executes in-browser
  5. Impact
    Hijack session / act as victim

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated session with at least low-level privileges (CVSS PR:L) to submit input into an affected, improperly-neutralized field of the web application; it cannot be performed by a fully unauthenticated attacker. Although the supplied vector states UI:N, successful script execution realistically depends on a second user rendering the injected content, which limits reliability and scope. The precise feature or input field, the affected product, and whether the flaw is stored or reflected are not identifiable from the input because the product metadata is corrupted (listed as 'CAPEC-63'); impact is bounded to versions before 3.0b63 of that unidentified Johnson Controls component.

Impact

This is a stored/reflected cross-site scripting flaw (CWE-79) with a reported CVSS 4.0 base score of 5.8 (Medium). The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates network-reachable, low-complexity exploitation but requires low-level privileges (PR:L) - so the attacker must be authenticated. The 'E:P' exploit-maturity metric in the supplied vector signals that proof-of-concept exploit code exists; this is NOT the same as active exploitation. No CISA KEV listing and no EPSS score were provided, so widespread automated exploitation cannot be confirmed. Two signals conflict with the vector: the vector asserts UI:N (no user interaction), yet XSS realistically requires a victim to render the injected content, and the subsequent-system impacts (SC:H/SI:H/SA:H) look inflated for a typical XSS that executes in a victim's browser session - verify these with the vendor. Most critically, the product identity is corrupted: the affected 'product' is listed as 'CAPEC-63' (an attack-pattern catalog ID) and the CPE vendor is 'cwe-79_-_cross-site_scripting' (a weakness ID), neither of which is a real product or vendor. The reporter ('jci') and the sole reference (johnsoncontrols.com trust center) point to Johnson Controls, but the actual affected product cannot be determined from this data. Net assessment: a medium-severity, authenticated XSS with PoC code but no confirmed in-the-wild exploitation - a routine patch-prioritization item, not an emergency, pending resolution of the garbled product metadata.

Exploit ScenarioDerived

An authenticated low-privilege user of the affected Johnson Controls web application submits input containing a crafted script payload into a field that is not properly neutralized before being rendered in a web page. When another user (potentially an administrator) views the page, the script executes in their browser session, enabling session hijacking or actions in their context. Proof-of-concept exploit code is indicated by the CVSS exploit-maturity metric (E:P).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

Cross-site scripting (CWE-79) in an unidentified Johnson Controls web application component affects builds prior to 3.0b63, allowing an attacker with a low-privileged authenticated session (CVSS PR:L) to submit crafted input into a field that is rendered to other users without proper neutralization. The reported CVSS 4.0 base score is 5.8 (Medium), with scope-change metrics (SC:H/SI:H/SA:H) indicating the impact can extend beyond the vulnerable component into the browser session or downstream consumers of the page. The affected product cannot be pinned down from the source data because the CPE entry resolves to a generic classification label ('CWE-79 - Cross-site Scripting' / 'CAPEC-63') rather than a real product name, so the specific Johnson Controls offering, the vulnerable feature, and whether the flaw is stored or reflected remain unconfirmed; the only vendor reference is the Johnson Controls cybersecurity advisory page. There is no confirmed CISA KEV listing (not confirmed actively exploited (CISA KEV)), but the CVSS 4.0 Exploit Maturity value of Proof-of-Concept (E:P) indicates publicly available exploit code exists, and our independent assessment notes that reliable exploitation depends on a second user rendering the injected content, which limits reliability and scope.

RemediationAI

Patch status is ambiguous and must be verified with the vendor: no advisory text specifying an exact fixed release is included in the input, and the description's "before 3.0b63" only implies that 3.0b63 or later is the remediated build - that inference is not independently confirmed, so no exact fix version should be treated as authoritative until checked against https://www.johnsoncontrols.com/trust-center/cybersecurity/security-advisories. Operators of Johnson Controls deployments should identify the specific product and build from that advisory, then upgrade to the vendor-designated fixed release, and contact Johnson Controls support if the installed product cannot be matched to a published affected version. Where patching is delayed, the practical compensating controls for this CWE-79 class are: apply context-aware output encoding and strict input validation to the affected field (trade-off: requires identifying the exact sink, which the corrupted metadata currently prevents, so coordinate with the vendor), deploy a Content-Security-Policy with a nonce or hash-based script-src and no 'unsafe-inline' (trade-off: breaks inline scripts and third-party widgets until audited), set session cookies HttpOnly and SameSite=Strict or Lax to blunt token theft (trade-off: Strict can break cross-site SSO and embedded flows), and temporarily restrict which low-privileged roles may write to the affected field or endpoint (trade-off: reduces functionality for legitimate users). A WAF XSS ruleset can be added for interim coverage but is bypassable and should not be the primary control. Detection should focus on anomalous script content or unexpected markup in stored user-supplied fields and on outbound requests from browsers to unfamiliar domains.

Affected VersionsENISA

CAPEC-63 0 <3.0b63

Affected Packages

euvd capec_63 fix: 3.0b63

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-79, improper neutralization of input during web page generation: the application accepts data from an authenticated low-privileged user (PR:L in the supplied CVSS:4.0 vector, AV:N/AC:L/AT:N) and emits it into an HTML response without context-appropriate encoding, so browser-side script executes in the security context of the page that serves it. CAPEC-63 is the attack pattern 'Cross-Site Scripting (XSS)', and its appearance here as the affected 'product' alongside CWE-79 confirms a data-quality defect in the source feed - CWE and CAPEC are classification identifiers, not software - which is why the CPE string cpe:2.3:a:cwe-79_-_cross-site_scripting:capec-63:*:*:*:*:*:*:*:* matches a placeholder rather than a deployable component. The scope-change metrics (SC:H/SI:H/SA:H) are the technically significant part of the vector: XSS impact is normally confined to the user's browser session, so a high subsequent-system rating implies session token theft, CSRF-style action forgery, or influence over other users' authenticated workflows rather than mere defacement. Note the discrepancy between the supplied vector's UI:N and our assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N - the authoritative assessment treats user interaction (a victim rendering the payload) as required, and correspondingly bounds impact to low confidentiality and integrity with no availability impact. The E:P exploit-maturity rating reflects proof-of-concept code, which is distinct from confirmed in-the-wild exploitation.

Know when Johnson Controls gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (jci) PRIMARY 5.8 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:H/SI:H/SA:H/E:P
vuln.today AI 5.4 MEDIUM

Authenticated low-priv attacker injects (PR:L); victim must render the payload (UI:R); script escapes into the victim's browser context (S:C) with limited C/I and no availability impact.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (jci).

CVSS VectorVendor: jci

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

Lifecycle Timeline

1
Patch available
Oct 01, 2026 - 22:18 EUVD

DescriptionCVE.org

Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in CWE-79 - Cross-site Scripting CAPEC-63 allows Cross-Site Scripting (XSS).

This issue affects CAPEC-63: before 3.0b63.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

29
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +29
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2026-71449 CRITICAL
9.3 Oct 01

Hard-coded cryptographic key in Johnson Controls EasyIO FS32 building automation controllers before firmware 3.0b63 perm

CVE-2026-64893 HIGH
7.3 Oct 01

Cleartext transmission of sensitive information in Johnson Controls EasyIO NEO (all versions before 3.3b25) lets an atta

CVE-2026-21653 HIGH
7.2 Jul 23

Server-Side Request Forgery in Johnson Controls CCure 9000 and the victor application server (versions 2.9 through 3.0)

CVE-2026-34496 HIGH
7.1 Jul 23

Privilege management weakness in Johnson Controls victor Web (video management client) on Windows lets a high-privileged

CVE-2026-34492 HIGH
7.0 Aug 14

External control of file name or path (CWE-73) in Johnson Controls Airwall before version 4.1 enables file manipulation

CVE-2026-64887 HIGH
7.0 Aug 14

Hard-coded cryptographic key exposure in Johnson Controls Airwall before version 4.1 enables local attackers to conduct

CVE-2026-27875 MEDIUM
6.9 Aug 21

Cleartext credential exposure in Johnson Controls Simplex Incident Manager / Autocall Fire Administrator (all versions b

CVE-2025-43876 HIGH
8.7 Dec 24

OS command injection in Johnson Controls devices can allow a low-privilege authenticated remote attacker to execute arbi

CVE-2025-43875 HIGH
8.7 Dec 24

Command injection in certain Johnson Controls devices allows a low-privilege authenticated attacker to execute arbitrary

CVE-2026-34499 HIGH
8.5 Oct 07

Hard-coded cryptographic key material embedded in Johnson Controls ADVMS builds prior to 3.10 lets a locally authenticat

CVE-2026-71456 HIGH
8.5 Oct 26

Use of a hard-coded cryptographic key in Johnson Controls Kantech EntraPass before 9.20 enables a padding oracle crypto

CVE-2026-64892 MEDIUM
6.3 Oct 01

Information disclosure in Johnson Controls Easy IO Neo versions before 3.3b63 allows an authenticated high-privileged at

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy