This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Modx Revolution
MODX Revolution through v2.7.0-pl allows XSS via a document resource (such as pagetitle), which is mishandled during an Update action, a Quick Edit action, or the viewing of manager logs. (2019-02-06, CVE-2018-20756)
MODX Revolution through v2.7.0-pl allows XSS via an extended user field such as Container name or Attribute name. (2019-02-06, CVE-2018-20757)
MODX Revolution through v2.7.0-pl allows XSS via the User Photo field. (2019-02-06, CVE-2018-20755)
MODX Revolution through v2.7.0-pl allows XSS via User Settings such as Description. (2019-02-06, CVE-2018-20758)
MODX Revolution v2.6.5-pl allows stored XSS via a Create New Media Source action. (2018-09-26, CVE-2018-17556)
MODX Revolution 2.6.3 has XSS. (2018-06-01, CVE-2018-10382)
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>