Skip to content

Commit 8a75097

Browse files
authored
Update title
1 parent ad71777 commit 8a75097

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

_posts/2024-09-01-stored-xss-on-seedr-cc.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: How I Discovered a stored Self-XSS Vulnerability in Seedr.cc and Its Impact
3-
description: This blog shares my journey of uncovering a Self-XSS vulnerability in Seedr.cc and how the vulnerability, typically considered less severe, can still have significant impacts.
2+
title: Discovering a Stored XSS Vulnerability in Seedr.cc
3+
description: This blog details my journey of uncovering a stored XSS vulnerability in Seedr.cc
44
author: hemantapkh
55
date: 2024-09-01 02:41:18 +0000
66
categories: [Cybersecurity]
@@ -61,7 +61,7 @@ After adding this magnet link on my Seedr account, my XSS vector was permanently
6161

6262
## Impact
6363

64-
This vulnerability could have severe implications, including account takeovers via malicious JavaScript injections. Although the XSS vulnerability I discovered is a type of Self-XSS, meaning it executes only in the context of the user who submits the payload, it can still be exploited to target other users.
64+
This vulnerability could have severe implications, including account takeovers via malicious JavaScript injections. While the XSS vulnerability I discovered is a type of Self-XSS, meaning it executes only in the context of the user who submits the payload, it can still be exploited to target other users.
6565

6666
Imagine someone injecting the similar script into a magnet link and sharing it with unsuspecting victims:
6767

0 commit comments

Comments
 (0)