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 in EspoCRM-5.3.6 #1039

Closed
security-breachlock opened this issue Sep 13, 2018 · 3 comments
Closed

Stored XSS in EspoCRM-5.3.6 #1039

security-breachlock opened this issue Sep 13, 2018 · 3 comments
Milestone

Comments

@security-breachlock
Copy link

security-breachlock commented Sep 13, 2018

Affected software: EspoCRM-5.3.6

Type of vulnerability: Stored XSS

Discovered by: BreachLock

Website: https://www.breachlock.com

Author: Balvinder Singh

Description: Stored attacks are those where the injected script is permanently stored on the target servers, such as in a database, in a message forum, visitor log, comment field, etc. The victim then retrieves the malicious script from the server when it requests the stored information. Stored XSS is also sometimes referred to as Persistent or Type-I XSS.

Proof of concept:
Step1: Login into the CRM and in the mailbox use the link for entering the malicious javascript into it and save it as a draft message and whenever you open the draft msg the malicious javascript will get executed.

link_xss_1_param_
xss1_link_execute

VulnerableURL: http://localhost/EspoCRM-5.3.6/EspoCRM-5.3.6/#Email/view/5b962f8e6f2e91033

@yurikuzn
Copy link
Contributor

Fix: be62cae

@security-breachlock
Copy link
Author

Hi,

Thanks for your positive response,

Did you use CVE ID to track these bugs?

Looking forward to hearing from you.

@fgeek
Copy link

fgeek commented Sep 28, 2018

CVE-2018-17302 has been assigned for this vulnerability.

@yurikuzn yurikuzn added this to the Version 5.4.3 milestone Sep 28, 2018
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

3 participants