CVE-2023-6710: Red Hat JBoss Core Services for RHEL 8 · Cross-site Scripting
Affects Red Hat JBoss Core Services for RHEL 8Source CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 12 Dec 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by redhat
, 16 hours before disclosure
CVE published
on cve.org
, t = 0
First Exploit-DB entry (opens in a new tab)
Apache mod_proxy_cluster 1.2.6 - Stored XSS
, 153 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
AI-suggested
European organizations should implement the following specific mitigations: 1) Apply official patches from Red Hat as soon as they become available; monitor Red Hat security advisories closely. 2) If patches are not yet available, restrict access to the cluster-manager interface to trusted administrators only, ideally via VPN or internal networks, to limit exposure. 3) Implement strict input validation and output encoding on the 'alias' parameter within mod_proxy_cluster configurations to prevent injection of malicious scripts. 4) Employ web application firewalls (WAFs) with rules targeting XSS payloads on the affected endpoints. 5) Conduct regular security audits and penetration testing focused on management interfaces to detect potential injection points. 6) Educate administrators about the risks of clicking untrusted URLs that may contain malicious parameters. 7) Review and harden user privilege assignments to minimize the number of users with access to mod_proxy_cluster management functions. 8) Monitor logs for suspicious activity related to the cluster-manager page and unusual URL parameters. These targeted actions go beyond generic advice and address the specific attack vector and affected component.
Description
A flaw was found in the mod_proxy_cluster in the Apache server. This issue may allow a malicious user to add a script in the 'alias' parameter in the URL to trigger the stored cross-site scripting (XSS) vulnerability. By adding a script on the alias parameter on the URL, it adds a new virtual host and adds the script to the cluster-manager page.
References
- access.redhat.com/errata/RHSA-2024:1316 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:1317 (opens in a new tab)
- access.redhat.com/errata/RHSA-2024:2387 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2023-6710 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2254128 (opens in a new tab)