This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Frog Cms
Frog CMS 1.1 is affected by: Cross Site Scripting (XSS). The impact is: Cookie stealing, Alert pop-up on page, Redirecting to another phishing site, Executing browser exploits. The component is: Snippets. (2019-07-22, CVE-2019-1010235)
admin/?/plugin/file_manager in Frog CMS 0.9.5 allows XSS by creating a new file containing a crafted attribute of an IMG element. (2019-02-11, CVE-2018-20778)
Frog CMS 0.9.5 has XSS via the admin/?/layout/edit/1 Body field. (2019-02-11, CVE-2018-20774)
Frog CMS 0.9.5 has XSS via the admin/?/snippet/edit/1 Body field. (2019-02-11, CVE-2018-20777)
Frog CMS 0.9.5 allows XSS via the forgot password page (aka the /admin/?/login/forgot URI). (2019-01-12, CVE-2019-6243)
Frog CMS 0.9.5 has XSS in the admin/?/page/edit/1 body field. (2019-01-09, CVE-2018-20680)
Frog CMS 0.9.5 has XSS via the Database name field to the /install/index.php URI. (2018-12-25, CVE-2018-20448)
Frog CMS 0.9.5 has stored XSS via /admin/?/plugin/comment/settings. (2018-09-03, CVE-2018-16374)
Frog CMS 0.9.5 has XSS via the /admin/?/user/add Name or Username parameter. (2018-04-11, CVE-2018-9991)
Frog CMS 0.9.5 has XSS via the name field of a new "File" or "Directory" on the admin/?/plugin/file_manager/browse/ screen. (2018-04-11, CVE-2018-9992)
Why Cross-site Scripting can be dangerous
Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.
The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:
https://server.com/confirmation?message=Transaction+Complete
what results in:
<span>Confirmation: Transaction Complete</span>
In that case the message can be modified to become a valid Javascript code, e.g.:
https://server.com/confirmation?message=<script>dangerous javascript code here</script>
and it will be executed locally by the user's browser with full access to the user's personal application/browser data:
<span>Confirmation: <script>dangerous javascript code here</script></span>