Loadbalancer.org Enterprise VA MAX before 8.3.3 has XSS because Apache HTTP Server logs are displayed.

published 2018-11-20 7y ago modified 2026-06-17 4mo ago also EUVD-2018-10575

cvss: 9.6; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.6%; EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits: 0; none known

Patch / fix

fixed in 1

loadbalancer enterprise_va_max 8.3.3

Is CVE-2018-18864 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

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

Exploits and checks

packetstormsecurity.com http://packetstormsecurity.com/files/150135/Loadbalancer.org-Enterprise-VA-MAX-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
seclists.org http://seclists.org/fulldisclosure/2018/Nov/5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	9.6	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

packetstormsecurity.com /files/150135/Loadbalancer.org-Enterprise-VA-MAX-Cross-Site-Scripting.html
exploit, third-party-advisory, vdb-entry
seclists.org /fulldisclosure/2018/Nov/5
mailing-list, exploit, third-party-advisory

Sources

CVE List CVE-2018-18864
NVD CVE-2018-18864

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.