Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XSS + CSRF - Admin account takeover #57

Closed
frostnull opened this issue Oct 29, 2019 · 1 comment
Closed

XSS + CSRF - Admin account takeover #57

frostnull opened this issue Oct 29, 2019 · 1 comment

Comments

@frostnull
Copy link

frostnull commented Oct 29, 2019

Title

Description

  • A number of factors lead to an attack that could compromise an admin user account. The following steps describe how to achieve it.
    First, the functionality in question is vulnerable to XSS attacks in the field responsible for changing the page header. Due to the fact that this feature does not have any anti CSRF token (https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)) an attack using an auto-submit form containing XSS is feasible. thema in question .. as aggravating none of the admin user session tokens, they are protected with the HTTP only flag, ie they can be caught via scripting languages.

POC

The following two demos illustrate respectively, direct insertion via functionality, and shortly after a proof of concept using an attacker's domain site and the victim (in this case the admin) by clicking on the form containing the same request to fire and persist a XSS on your blog homepage

  • XSS vulnerable endpoint

csrf_01

  • Attack POC

csrf_xss

@vzuburlis
Copy link
Member

Nice find. Values for theme options should not accept tags by default.
The csrf attack shall be avoided with the stricted sessionId cookie. These changes applied at version 1.11.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants