How severe is GHSA-25v4-mcx4-hh35?

No CVSS score has been assigned to GHSA-25v4-mcx4-hh35 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-25v4-mcx4-hh35?

GHSA-25v4-mcx4-hh35 affects the following packages: atlasboard-atlassian-package (npm). Ecosystems affected: npm.

How do I fix GHSA-25v4-mcx4-hh35?

No patched version of atlasboard-atlassian-package has shipped for GHSA-25v4-mcx4-hh35 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-25v4-mcx4-hh35 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for atlasboard-atlassian-package, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-25v4-mcx4-hh35 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-25v4-mcx4-hh35 actively exploited in the wild?

No public exploit code has been indexed for GHSA-25v4-mcx4-hh35 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.

When was GHSA-25v4-mcx4-hh35 published, and has it been updated?

GHSA-25v4-mcx4-hh35 was published on September 4, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Cross-Site Scripting in atlasboard-atlassian-packageGHSA-25v4-mcx4-hh35

GHSA-25v4-mcx4-hh35 is a security vulnerability in atlasboard-atlassian-package. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 4, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

atlasboard-atlassian-packagenpm

8downloads / week

Description

All versions of atlasboard-atlassian-package prior to 0.4.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly sanitize user input that is rendered as HTML, which may allow attackers to execute arbitrary JavaScript in a victim's browser. This requires attackers being able to change issue summaries in Jira tickets.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`atlasboard-atlassian-package`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for atlasboard-atlassian-package, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of atlasboard-atlassian-package has shipped for GHSA-25v4-mcx4-hh35 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

All versions of `atlasboard-atlassian-package` prior to 0.4.2 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly sanitize user input that is rendered as HTML, which may allow attackers to execute arbitrary JavaScript in a victim's browser. This requires attackers being able to change issue summaries in Jira tickets. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-25v4-mcx4-hh35 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works