Loading HuntDB...

Stored XSS on Broken Themes via filename

Low
W
WordPress
Submitted None
Reported by apapedulimu

Vulnerability Details

Technical details and impact analysis

Cross-site Scripting (XSS) - Stored
Hi, I've found something here, ##Description XSS Stored because filename of theme when broken, So when theme is broken, Wordpress will inform the name of theme who has been broken which is the folder name of theme and inform the error with description message. {F342862} Looks like the filename is reflected, on the `Name` of the detail broken themes. I try to rename the folder to malicious name ( payload : <img src=x onerror=alert(1)> ) and the payload it'll be execute. {F342863} ##POC 1. Upload theme 1. Delete the style.css ( or you can make new folder on theme path with payload name ) 1. Rename the folder to `<img src=x onerror=alert(1)>` 1. See theme page. ##Video https://youtu.be/IuJrcR_BoKo ## Impact XSS will be execute , because the filename is stored on page without any filter, and this is possible to make stored XSS. It'll be good to filter / encoding the illegal character, like wordpress do on themes upload.

Report Details

Additional information and metadata

State

Closed

Substate

Resolved

Submitted

Weakness

Cross-site Scripting (XSS) - Stored