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

Stored XSS via blog #794

Closed
y-mehta opened this issue Feb 16, 2018 · 1 comment
Closed

Stored XSS via blog #794

y-mehta opened this issue Feb 16, 2018 · 1 comment

Comments

@y-mehta
Copy link

y-mehta commented Feb 16, 2018

Description:
Cross-site scripting (XSS) vulnerability in Gleez CMS might allow remote attackers (users) to inject arbitrary web script or HTML via the source editor, which will result in Stored XSS when an Administrator tries to edit the post.

Vulnerability Type: Stored XSS

Attack Vectors:

  1. Login as user on Gleez CMS
  2. Click on Blogs -> Add Blog
  3. Change to HTML mode in content box.
  4. Add XSS Payload : <img src="x" onerror="alert(document.domain)" style="">
  5. Save the blog.
  6. Login as Administrator
  7. Goto Blogs
  8. Open the malicious blog and click on edit.
  9. XSS!

Attack Impact:
This could be used to perform actions against the administrators (or any user editing that post) and could potentially lead to hijacking the user’s session/token. This could happen by users navigating to the attacker’s post on their own, or by the attacker somehow persuading the victim to navigate to the post.

Note: It'll not result into XSS in the normal view mode, but when admin or other user will try to edit the post code will be executed.[Stored XSS from User to Admin.]

Assigned CVE: CVE-2018-7035

sandeepone added a commit that referenced this issue Jul 5, 2018
Thanks for pointing the bug #794 #796. by @y-mehta @levoncf
@sandeepone
Copy link
Member

My apologies for not looking into this issue, some how it got skipped. Thanks for bringing to our notice. I've disabled Redactor immediately.

@y-mehta y-mehta closed this as completed Jan 23, 2020
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