Security Fix for Cross-Site Scripting (XSS) - huntr.dev #2158
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
https://huntr.dev/users/arjunshibu has fixed the Cross-Site Scripting (XSS) vulnerability🔨 . Think you could fix a vulnerability like this?
Get involved at https://huntr.dev/
Q | A
Version Affected | ALL
Bug Fix | YES
Original Pull Request | 418sec#1
Vulnerability README | https://github.com/418sec/huntr/blob/master/bounties/npm/apexcharts/1/README.md
User Comments:
Bounty URL: https://www.huntr.dev/bounties/1-npm-apexcharts
apexchartsis vulnerable to Cross-Site Scripting (XSS).The package does not properly validate some chart fields. This causes
XSSand the payload is triggered whentooltipandlabelfields are rendered. The fix is implemented by sanitizing those fields before rendering them.JSand insert the XSS payload below in thenamefield'sales<img src=x onerror=alert(1)>'Build package to apply fix
npm run dev # or npm run buildXSS is fixed as shown below.



+1 User Acceptance Testing (UAT)