-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XSS Vulnerability in Javascript: string #709
Comments
pzyc0k
changed the title
XSS Vulnerability in <href> label
XSS Vulnerability in Javascript: string
Aug 2, 2019
Why are you using |
Can you try against this version please, also be sure the have the iframe filter enabled: |
alromh87
added a commit
to alromh87/editor.md
that referenced
this issue
Sep 10, 2020
fixes #pandao#612 fixes #pandao#662 fixes #pandao#697 fixes #pandao#700 fixes #pandao#701 fixes #pandao#709 fixes #pandao#715 fixes #pandao#764 fixes #pandao#816 ### Probably: fixes #pandao#307 fixes #pandao#560
alromh87
added a commit
to alromh87/editor.md
that referenced
this issue
Sep 10, 2020
fixes #pandao#612 fixes #pandao#662 fixes #pandao#697 fixes #pandao#700 fixes #pandao#701 fixes #pandao#709 fixes #pandao#715 fixes #pandao#764 fixes #pandao#816 fixes #pandao#307 fixes #pandao#560
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test Environment
Google Chrome - Version 75.0.3770.142 (Official Build) (64-bit)
Description
A malicious actor may insert and finally execute malicious Javascript code.
Steps to reproduce
Impact
If an attacker can control a script that is executed in the victim's browser, then they can typically fully compromise that user.
Expected Results
No malicious Javascript code should be executed
Remediation
In general, it is highly recommended to implement input validation, output sanitization and escaping.
Proof-of-Concept
The text was updated successfully, but these errors were encountered: