Example:
1 Like
It sounds like you’re encountering an issue where, after successfully injecting an XSS payload, the HTML tags aren’t being parsed as intended. This can happen for a few reasons, so here are some things to consider:
-
HTML Tag Filtering or Escaping:
- The application might be filtering or escaping your HTML tags, which would prevent them from being parsed and displayed correctly. Check if the application is encoding characters like
<
,>
, and/
into their HTML entity equivalents (e.g.,<
,>
,/
), which would cause the tags to appear as plain text rather than being rendered as HTML.
- The application might be filtering or escaping your HTML tags, which would prevent them from being parsed and displayed correctly. Check if the application is encoding characters like
-
Content Security Policy (CSP):
- A strict Content Security Policy might be in place, blocking your script from running or the HTML from rendering. You can inspect the CSP headers in the network tab of your browser’s developer tools. If you find that CSP is the issue, you may need to adjust your payload or try injecting in a different context.
-
Output Context:
- Make sure that your XSS payload is being injected into a context where HTML is allowed to be parsed. If the injection point is within an attribute, a script, or another context that doesn’t support raw HTML, the tags won’t render as expected.
-
Input Sanitization:
- The application might have strong sanitization in place, stripping out or altering your payload. Try experimenting with different payloads or encoding techniques to bypass these defenses.
-
Web Application Firewall (WAF):
- If a WAF is present, it might be interfering with your payload. In this case, you could try various evasion techniques, such as using different encodings or less common tags/attributes to avoid detection.