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

Non-Persistent or Type-II XSS in EspoCRM-5.3.6 #1038

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

Non-Persistent or Type-II XSS in EspoCRM-5.3.6 #1038

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

Comments

@security-breachlock
Copy link

security-breachlock commented Sep 13, 2018

Affected software: EspoCRM-5.3.6

Type of vulnerability: Non-Persistent or Type-II XSS

Discovered by: BreachLock

Website: https://www.breachlock.com

Author: Balvinder Singh

Description: Reflected attacks are those where the injected script is reflected off the web server, such as in an error message, search result, or any other response that includes some or all of the input sent to the server as part of the request. Reflected attacks are delivered to victims via another route, such as in an e-mail message, or on some other website. When a user is tricked into clicking on a malicious link, submitting a specially crafted form, or even just browsing to a malicious site, the injected code travels to the vulnerable website, which reflects the attack back to the user’s browser. The browser then executes the code because it came from a "trusted" server. Reflected XSS is also sometimes referred to as Non-Persistent or Type-II XSS.

Proof of concept:
Step1: Login to the CRM.
Step2: In the search panel, use the malicious javascript and hit enter the code will get executed successfully.

1 ref
1 ref 2

VulnerableURL: http://localhost/EspoCRM-5.3.6/EspoCRM-5.3.6/#Account

@yurikuzn
Copy link
Contributor

Thanks for reporting.

Fix: eabd52b

@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.

@yurikuzn
Copy link
Contributor

Hi,

No, We didn't use CVE IDs.

@fgeek
Copy link

fgeek commented Sep 28, 2018

CVE-2018-17301 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