How severe is GHSA-7j6x-42mm-p7jm?

GHSA-7j6x-42mm-p7jm has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7j6x-42mm-p7jm?

GHSA-7j6x-42mm-p7jm affects the following packages: github.com/zincsearch/zincsearch (Go), github.com/zinclabs/zinc (Go). Ecosystems affected: Go.

How do I fix GHSA-7j6x-42mm-p7jm?

Update github.com/zincsearch/zincsearch to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7j6x-42mm-p7jm is resolved across your whole dependency graph.

How do I detect GHSA-7j6x-42mm-p7jm in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zincsearch/zincsearch. 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.

How do I mitigate GHSA-7j6x-42mm-p7jm if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-7j6x-42mm-p7jm?

O3 pinpoints whether GHSA-7j6x-42mm-p7jm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7j6x-42mm-p7jm actively exploited in the wild?

No public exploit code has been indexed for GHSA-7j6x-42mm-p7jm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7j6x-42mm-p7jm?

GHSA-7j6x-42mm-p7jm has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 42th 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.

When was GHSA-7j6x-42mm-p7jm published, and has it been updated?

GHSA-7j6x-42mm-p7jm was published on July 6, 2023 and was last updated on August 20, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-7j6x-42mm-p7jm: Zinc Cross-site Scripting vulnerability (M…

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk42th percentile+0.12%

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

2 pkgs affected

🐹github.com/zincsearch/zincsearch🐹github.com/zinclabs/zinc

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

Description

In Zinc, versions v0.1.9 through v0.3.1 are vulnerable to Stored Cross-Site Scripting when using the delete template functionality. When an authenticated user deletes a template with a XSS payload in the name field, the Javascript payload will be executed and allow an attacker to access the user’s credentials.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/zincsearch/zincsearch`	≥ 0.1.9&&< 0.3.2	0.3.2
🐹Go	`github.com/zinclabs/zinc`	≥ 0.1.9&&< 0.3.2	0.3.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zincsearch/zincsearch. 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.
Fix
Update github.com/zincsearch/zincsearch to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7j6x-42mm-p7jm is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-7j6x-42mm-p7jm 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-7j6x-42mm-p7jm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Zinc, versions v0.1.9 through v0.3.1 are vulnerable to Stored Cross-Site Scripting when using the delete template functionality. When an authenticated user deletes a template with a XSS payload in the name field, the Javascript payload will be executed and allow an attacker to access the user’s credentials.

O3 Security · Impact-Aware SCA

Is GHSA-7j6x-42mm-p7jm in your dependencies?

O3 detects GHSA-7j6x-42mm-p7jm across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-7j6x-42mm-p7jm