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
Github issue tracker is used for bug only. For general questions and requests, please join the Google group
Don't hesitate to provide screenshots.
v1.0
Acronym is just a normal form parameter, but if I modify the length of that column in database, I can input a longer XSS payload
And when next time I look at the page, a XSS vulnerability is pop out.
Details can be seen in the following docx. jorani.docx
The text was updated successfully, but these errors were encountered:
This "attack" is very unlikely to happen. you need to access the db and then edit db column, but who would edit the lenght of acronym ??? And then you need to have admin privileges to exploit it
I will add a limit but no panic :)
Sorry, something went wrong.
93634b7
Jorani?
Thanks! I found it exploitable because there is already existed a SQL vuln(CVE-2022-34132), so maybe the attacker can use it to control the db column.
bbalet
No branches or pull requests
Github issue tracker is used for bug only.
For general questions and requests, please join the Google group
Don't hesitate to provide screenshots.
What is the version of Jorani?
v1.0
Expected behavior
Acronym is just a normal form parameter, but if I modify the length of that column in database, I can input a longer XSS payload

Actual behavior
And when next time I look at the page, a XSS vulnerability is pop out.

Steps to reproduce the behavior
Details can be seen in the following docx.
jorani.docx
The text was updated successfully, but these errors were encountered: