Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-5xgh-643p-cp2g

MEDIUM

GHSA-5xgh-643p-cp2g is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in yapi-vendor. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-5xgh-643p-cp2g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-site Scripting in yapi-vendor

Also known asCVE-2018-17574
Published
Nov 21, 2018
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

yapi-vendornpm
817downloads / week

Description

An issue was discovered in YMFE YApi 1.3.23. There is stored XSS in the name field of a project.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmyapi-vendorall versions1.3.23
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 yapi-vendor. 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 yapi-vendor to 1.3.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5xgh-643p-cp2g 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-5xgh-643p-cp2g 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-5xgh-643p-cp2g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in YMFE YApi 1.3.23. There is stored XSS in the name field of a project.
O3 Security · Impact-Aware SCA

Is GHSA-5xgh-643p-cp2g in your dependencies?

O3 detects GHSA-5xgh-643p-cp2g across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.