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

Phalcon Eye - Multiple Cross-Site Scripting (XSS) #133

Open
bestshow opened this issue Feb 10, 2017 · 3 comments
Open

Phalcon Eye - Multiple Cross-Site Scripting (XSS) #133

bestshow opened this issue Feb 10, 2017 · 3 comments

Comments

@bestshow
Copy link

bestshow commented Feb 10, 2017

Procuct: Phalcon Eye
Vendor: Phalcon (https://phalconphp.com/)
Vunlerable Version: 0.4.1 and probably prior
Tested Version: 0.4.1
Author: ADLab of Venustech

Advisory Details:
I have discovered Multiple Cross-Site Scripting (XSS) in Phalcon Eye, which can be exploited to add,modify or delete information in application`s database and gain complete control over the application.

The vulnerability exists due to insufficientfiltration of user-supplied data in multiple HTTP GET parameters passed to “phalconeye-master/phalconeye-master/public/external/pydio/plugins/editor.webodf/frame.php” url. An attacker could execute arbitrary HTML and script code in browser in context of the vulnerable website.
The exploitation examples below uses the "alert()" JavaScript function to see a pop-up messagebox:
(1)
http://localhost/testcmsofgithub/phalconeye-master/phalconeye-master/public/external/pydio/plugins/editor.webodf/frame.php?token=%22%22);}%3C/script%3E%3Cscript%3Ealert(1);%3C/script%3Efunction%20nopfun(){//
(2)
http://localhost/testcmsofgithub/phalconeye-master/phalconeye-master/public/external/pydio/plugins/editor.webodf/frame.php?file=%22%22);}%3C/script%3E%3Cscript%3Ealert(1);%3C/script%3Efunction%20nopfun(){//

@lantian
Copy link
Contributor

lantian commented Feb 10, 2017

Thanks for notify, I will publish fix for 0.4.1 and 0.5.0 branches.

Could you please help me assign a CVE for this issue?

How about PE-2017-0000001 ?

@bestshow
Copy link
Author

Hi:
Many thanks for your reply.

Bests.

@attritionorg
Copy link

Please note that is not a CVE assignment. It should be treated as a vendor-specific tracking ID. MITRE assigned CVE-2017-5960 to this.

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