This vulnerability lies in the 'add tags' function in the backend.
Try adding a tag, and we will name it an HTML code
Try adding it, and we will find that our HTML code has been successfully embedded in the front-end
Interestingly, when the administrator attempts to delete it, it will also trigger again(three times)
Of course, not only can img be used here, but it can also use more dangerous html code such as scripts.This may cause administrator COOKIE leakage or other more serious risks
In my previous issue submission, I mentioned the CSRF vulnerability.In my previous issue submission, I mentioned the CSRF vulnerability. In fact, it can be combined with XSS vulnerabilities.
We can generate such a CSRF POC
After the administrator triggers it, a tag with malicious HTML code will be generated in the background. When the administrator accidentally accesses the tag, it can cause an attack
This vulnerability lies in the 'add tags' function in the backend.

Try adding a tag, and we will name it an HTML code

Try adding it, and we will find that our HTML code has been successfully embedded in the front-end


Interestingly, when the administrator attempts to delete it, it will also trigger again(three times)



Of course, not only can img be used here, but it can also use more dangerous html code such as scripts.This may cause administrator COOKIE leakage or other more serious risks
In my previous issue submission, I mentioned the CSRF vulnerability.In my previous issue submission, I mentioned the CSRF vulnerability. In fact, it can be combined with XSS vulnerabilities.
We can generate such a CSRF POC


After the administrator triggers it, a tag with malicious HTML code will be generated in the background. When the administrator accidentally accesses the tag, it can cause an attack


<!-- github-sync-id:1690389750 -->
It seems that XSS vulnerabilities can also be triggered when editing tags
It seems that XSS vulnerabilities can also be triggered when editing tags


<!-- github-comment-id:1529383067 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This vulnerability lies in the 'add tags' function in the backend.

Try adding a tag, and we will name it an HTML code

Try adding it, and we will find that our HTML code has been successfully embedded in the front-end


Interestingly, when the administrator attempts to delete it, it will also trigger again(three times)



Of course, not only can img be used here, but it can also use more dangerous html code such as scripts.This may cause administrator COOKIE leakage or other more serious risks
In my previous issue submission, I mentioned the CSRF vulnerability.In my previous issue submission, I mentioned the CSRF vulnerability. In fact, it can be combined with XSS vulnerabilities.
We can generate such a CSRF POC


After the administrator triggers it, a tag with malicious HTML code will be generated in the background. When the administrator accidentally accesses the tag, it can cause an attack


Oh, I forgot, the affected version is the latest 13.6.0
It seems that XSS vulnerabilities can also be triggered when editing tags

