Security readout for executives and security teams
Plain-English summary
CVE-2017-9623 is a set of cross-site scripting flaws in Telaxus/EPESI 1.8.2 and earlier. An attacker could place malicious script or HTML into country data that later runs in a user's browser. Business impact depends on who can change or import that data and who views it.
Executive priority
Treat as a targeted remediation item, not an emergency, unless EPESI is internet-facing or stores user-controlled country data. Prioritize inventory, patch confirmation, and permission review.
Technical view
The CVE describes multiple XSS issues caused by crafted country data in Telaxus/EPESI 1.8.2 and earlier. Sources identify a GitHub issue and commit, but provide no CVSS, CWE, detailed affected CPEs, or confirmed fixed release in the supplied bundle.
Likely exposure
Exposure is likely limited to organizations running EPESI 1.8.2 or earlier. Risk is higher where untrusted users, integrations, or imports can modify country data and privileged staff view those records.
Exploitation context
The supplied sources do not show active exploitation, and the CVE is not listed as KEV. The described attack is remote XSS via crafted country data, but no exploit maturity or real-world targeting evidence is provided.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, exploit status, or fixed version is included. The strongest source evidence is the CVE description plus the Telaxus/EPESI GitHub issue and commit references.
Mitigation direction
- Identify any Telaxus/EPESI installations and confirm exact versions.
- Update EPESI to a vendor-fixed release or apply the referenced vendor commit after testing.
- Restrict who can create, import, or edit country data until remediated.
- Review vendor issue 186 for remediation context before production changes.
Validation and detection
- Verify no deployed EPESI instance is version 1.8.2 or earlier.
- Confirm the vendor fix commit is present in the deployed codebase.
- Review country data records for unexpected script or HTML content.
- Test that country fields render as inert text, not executable markup.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-9623 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Telaxus/EPESI/issues/186CVE reference · x_refsource_CONFIRM
- https://github.com/Telaxus/EPESI/commit/48fb5e81cd7a47d98bade092a5a72d8177621dbdCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.