Orchestration Designer Runtime Config XSS

published 2018-09-21 8y ago modified 2026-06-17 4mo ago also EUVD-2018-7484

cvss: 8.3; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

A cross-site scripting (XSS) vulnerability in the Runtime Config component of Avaya Aura Orchestration Designer could result in malicious content being returned to the user. Affected versions of Avaya Aura Orchestration Designer include all versions up to 7.2.1.

Patch / fix

fixed in 1 links 1

avaya aura_orchestration_designer 7.2.1

downloads.avaya.com/css/P8/documents/101052293 advisory

Is CVE-2018-15613 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 Fencer

Exploit prediction

0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	8.3	CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
NVD	3.0	6.1	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

Avaya Orchestration Designer

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

downloads.avaya.com /css/P8/documents/101052293
patch, vendor-advisory

Sources

CVE List CVE-2018-15613
NVD CVE-2018-15613

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.