You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A stored XSS vulnerability has been identified in DedeCMS V5.7.116.
Attackers can exploit this vulnerability by maliciously inserting an XSS payload in the comment section during the purchase of goods.
Details
The vulnerability is located in the file plus/carbuyaction.php. Our analysis indicates that all parameters are passed through the RemoveXSS method.
However, our payload can bypass the RemoveXSS method's filtering for XSS vulnerabilities, thus any script that relies solely on the RemoveXSS method to filter parameter values and displays these values on the page is vulnerable.
Steps
The attacker, posing as a regular user, purchases goods and adds a malicious comment.
An administrator opens the order details in the backend, triggering the stored XSS vulnerability.
Parameters that are vulnerable: des, postname, email, address.
It is worth noting that some parameters may have maximum length restrictions.
We provide a proof of concept that can bypass the RemoveXSS method:
<body onpointermove="alert(document.cookie)">
Of course, we can also bring in external js scripts by modifying the xss payload.
The text was updated successfully, but these errors were encountered:
Summary
A stored XSS vulnerability has been identified in DedeCMS V5.7.116.
Attackers can exploit this vulnerability by maliciously inserting an XSS payload in the comment section during the purchase of goods.
Details
The vulnerability is located in the file
plus/carbuyaction.php
. Our analysis indicates that all parameters are passed through theRemoveXSS
method.However, our payload can bypass the
RemoveXSS
method's filtering for XSS vulnerabilities, thus any script that relies solely on theRemoveXSS
method to filter parameter values and displays these values on the page is vulnerable.Steps
The attacker, posing as a regular user, purchases goods and adds a malicious comment.
An administrator opens the order details in the backend, triggering the stored XSS vulnerability.
POC
Parameters that are vulnerable:
des
,postname
,email
,address
.It is worth noting that some parameters may have maximum length restrictions.
We provide a proof of concept that can bypass the RemoveXSS method:
Of course, we can also bring in external js scripts by modifying the xss payload.
The text was updated successfully, but these errors were encountered: