StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9421610
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-23T21:27:23.007
FavoriteCount
0
LastActivityDate
2012-02-23T21:27:23.007
LastEditDate
LastEditorUserId
0
OwnerUserId
1167750
ParentId
9421414
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
<a href="http://danhilltech.tumblr.com/" rel="noreferrer">Dan Hill</a> wrote an <a href="http://www.tumblr.com/tagged/hack?before=1329947869" rel="noreferrer">article</a> about getting base64 hacked for WordPress installations. To quote the results of Dan's findings: <blockquote> The hack I found essentially created a new php file in the uploads folder of Wordpress that allowed remote filesystem control, and then modified the pages being served (every .php file) to include a script tag redirecting visitors to some dodgy sites. </blockquote> To get rid of the problem, <a href="http://danhilltech.tumblr.com/" rel="noreferrer">Dan</a> tried the following: <hr> I did this in three stages. First, find any world-writable directories (tsk tsk): <pre><code>find . -type d -perm -o=w </code></pre> And make them not world writable: <pre><code>find . -type d -perm -o=w -print -exec chmod 770 {} \; </code></pre> Delete all the new files these guys created: <pre><code>find . -wholename '*wp-content/uploads/*.php' -exec rm -rf {} \; </code></pre> (In wordpress, the uploads folder shouldn’t contain any PHP) Stage two, repair all your infected PHP files. I played around using sed and xargs for this, but eventually gave up and wrote a quick ruby script to do the job. Run this run this ruby script from your root directory: <pre><code>#!/usr/bin/env ruby Dir.glob('**/*.php').each do|f| puts f begin contents = File.read(f) contents = contents.gsub(/\<\?php \/\*\*\/ eval\(.*\)\);\?\>/, "") File.open(f, 'w') {|f| f.write(contents) } rescue puts "FILE ERROR" end end </code></pre> The final step is to upgrade all your old, forgotten about Wordpress installs to prevent any other vulnerabilities showing up. The bonus step for good luck is to reset your passwords, especially any MySQL passwords stored in plain text in your wp-config.php file. <hr> Hope Dan's findings help!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat exactly does this PHP exploit code (found on my app)?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsummea
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.