\n ```","datePublished":"2022-04-12T21:17:38Z","dateModified":"2025-12-10T00:42:25.426255Z","url":"https://o3.security/vulnerability/GHSA-5chx-gg25-v37m","inLanguage":"en","author":{"@id":"https://o3.security/#organization"},"publisher":{"@id":"https://o3.security/#organization"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://o3.security/vulnerability/GHSA-5chx-gg25-v37m"},"speakable":{"@type":"SpeakableSpecification","cssSelector":["h1",".vuln-summary",".vuln-severity",".vuln-mitigation"]},"about":[{"@type":"SoftwareApplication","name":"xain","applicationCategory":"Hex","softwareVersion":"0.6.2"}],"citation":[{"@type":"WebPage","url":"https://nvd.nist.gov/vuln/detail/CVE-2018-20302"},{"@type":"WebPage","url":"https://github.com/smpallen99/xain/issues/18"},{"@type":"WebPage","url":"https://github.com/dependabot/elixir-security-advisories/blob/master/packages/xain/2018-09-03.yml"}]}\n ```","url":"https://o3.security/vulnerability/GHSA-5chx-gg25-v37m","identifier":"GHSA-5chx-gg25-v37m","datePublished":"2022-04-12T21:17:38Z","dateModified":"2025-12-10T00:42:25.426255Z","inLanguage":"en","keywords":["GHSA-5chx-gg25-v37m","MEDIUM severity","CWE-79","CVE","vulnerability","security advisory"],"creator":{"@id":"https://o3.security/#organization"},"isAccessibleForFree":true,"variableMeasured":[{"@type":"PropertyValue","name":"CVSS Base Score","value":6.1,"description":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"},{"@type":"PropertyValue","name":"Severity","value":"MEDIUM"},{"@type":"PropertyValue","name":"EPSS Percentile","value":54}]}\n ```"}},{"@type":"Question","name":"How severe is GHSA-5chx-gg25-v37m?","acceptedAnswer":{"@type":"Answer","text":"GHSA-5chx-gg25-v37m has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance."}},{"@type":"Question","name":"Which packages are affected by GHSA-5chx-gg25-v37m?","acceptedAnswer":{"@type":"Answer","text":"GHSA-5chx-gg25-v37m affects the following packages: xain (Hex). Ecosystems affected: Hex."}},{"@type":"Question","name":"How do I fix GHSA-5chx-gg25-v37m?","acceptedAnswer":{"@type":"Answer","text":"Update xain to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5chx-gg25-v37m is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect GHSA-5chx-gg25-v37m in my Hex dependencies?","acceptedAnswer":{"@type":"Answer","text":"Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xain. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match."}},{"@type":"Question","name":"How do I mitigate GHSA-5chx-gg25-v37m if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands."}},{"@type":"Question","name":"How does O3 Security protect against GHSA-5chx-gg25-v37m?","acceptedAnswer":{"@type":"Answer","text":"O3 pinpoints whether GHSA-5chx-gg25-v37m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed."}},{"@type":"Question","name":"Is GHSA-5chx-gg25-v37m actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"Yes. There are 1 known exploit references for GHSA-5chx-gg25-v37m, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization."}},{"@type":"Question","name":"What is the EPSS score for GHSA-5chx-gg25-v37m?","acceptedAnswer":{"@type":"Answer","text":"GHSA-5chx-gg25-v37m has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 54th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority."}},{"@type":"Question","name":"What type of vulnerability is GHSA-5chx-gg25-v37m?","acceptedAnswer":{"@type":"Answer","text":"GHSA-5chx-gg25-v37m is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure."}},{"@type":"Question","name":"When was GHSA-5chx-gg25-v37m published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"GHSA-5chx-gg25-v37m was published on April 12, 2022 and was last updated on December 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
💧 Hex

GHSA-5chx-gg25-v37m

MEDIUM

Cross-site Scripting in xain

Also known asCVE-2018-20302
Published
Apr 12, 2022
Updated
Dec 10, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk54th percentile+0.65%
0.00%0.46%0.91%1.37%0.2%0.9%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
💧xain

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

XSS is possible via the use of the order query parameter. An example request would look like:

http://host/ressources?order=%27><script>alert(1);</script>

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💧Hexxainall versions0.6.2
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xain. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update xain to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5chx-gg25-v37m is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5chx-gg25-v37m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5chx-gg25-v37m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

XSS is possible via the use of the order query parameter. An example request would look like: ``` http://host/ressources?order=%27><script>alert(1);</script> ```
O3 Security · Impact-Aware SCA

Is GHSA-5chx-gg25-v37m in your dependencies?

O3 detects GHSA-5chx-gg25-v37m across Hex dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.