Vulnerabilities > Modx > Modx Revolution > Medium
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2019-02-06 | CVE-2018-20758 | Cross-site Scripting vulnerability in Modx Revolution MODX Revolution through v2.7.0-pl allows XSS via User Settings such as Description. | 5.4 |
2019-02-06 | CVE-2018-20757 | Cross-site Scripting vulnerability in Modx Revolution MODX Revolution through v2.7.0-pl allows XSS via an extended user field such as Container name or Attribute name. | 6.1 |
2019-02-06 | CVE-2018-20756 | Cross-site Scripting vulnerability 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. | 6.1 |
2019-02-06 | CVE-2018-20755 | Cross-site Scripting vulnerability in Modx Revolution MODX Revolution through v2.7.0-pl allows XSS via the User Photo field. | 6.1 |
2018-09-26 | CVE-2018-17556 | Cross-site Scripting vulnerability in Modx Revolution 2.6.5 MODX Revolution v2.6.5-pl allows stored XSS via a Create New Media Source action. | 5.4 |
2018-06-01 | CVE-2018-10382 | Cross-site Scripting vulnerability in Modx Revolution 2.6.3 MODX Revolution 2.6.3 has XSS. | 5.4 |
2017-11-17 | CVE-2017-1000223 | Cross-site Scripting vulnerability in Modx Revolution A stored web content injection vulnerability (WCI, a.k.a XSS) is present in MODX Revolution CMS version 2.5.6 and earlier. | 5.4 |
2017-08-29 | CVE-2015-6588 | Cross-site Scripting vulnerability in Modx Revolution Cross-site scripting (XSS) vulnerability in login-fsp.html in MODX Revolution before 1.9.1 allows remote attackers to inject arbitrary web script or HTML via the QUERY_STRING. | 6.1 |
2017-07-30 | CVE-2017-11744 | Cross-site Scripting vulnerability in Modx Revolution 2.5.7 In MODX Revolution 2.5.7, the "key" and "name" parameters in the System Settings module are vulnerable to XSS. | 6.1 |
2017-05-18 | CVE-2017-9071 | Cross-site Scripting vulnerability in Modx Revolution In MODX Revolution before 2.5.7, an attacker might be able to trigger XSS by injecting a payload into the HTTP Host header of a request. | 4.7 |