StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8963621
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-01-22T18:46:47.890
FavoriteCount
0
LastActivityDate
2012-01-22T18:46:47.890
LastEditDate
LastEditorUserId
0
OwnerUserId
53114
ParentId
8963279
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> Is this XSS? </blockquote> Yes, this is an <a href="https://www.owasp.org/index.php/Injection_Flaws">injection flaw</a> in general and would be referred to as a XSS exploit in this particular case as it’s JavaScript that was injected. But this injection flaw, where one user’s input gets reflected to other users without any changes, can also yield to other attacks like <a href="http://en.wikipedia.org/wiki/Website_defacement">defacement</a>. <blockquote> Would this work? </blockquote> Yes, it’s very likely that this would work as it’s the origin server that serves this code snipped just like any other code in the web page. So it’s like the author of the web site is the originator of this code and will be treated likewise. <blockquote> Are there any precautions developers should take against XSS other than escaping HTML? </blockquote> There are actually three different types of XSS: <a href="https://www.owasp.org/index.php/DOM_Based_XSS">DOM based XSS</a>, <a href="https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)#Reflected_XSS_Attacks">Reflected XSS</a>, and <a href="https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)#Stored_XSS_Attacks">Stored/persistent XSS</a>). Your example is a stored/persistend XSS exploit as the server deploys the exploit with every request. The general rule is not to trust any user input. That said either only valid user input should be allowed or the user input is filtered (removing invalid values) or properly encoded (convert invalid values) before outputting it. See <a href="https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet">OWASP’s XSS Cheat Sheet</a> for further information.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs user input of HTML with Javascript that is displayed to others but not HTML-escaped an example of a XSS
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGumbo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.