This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Domainmod
A cross site scripting (XSS) vulnerability in the /domains/cost-by-owner.php component of Domainmod 4.13 allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the "or Expiring Between" parameter. (2021-08-12, CVE-2020-20988)
A cross site scripting (XSS) vulnerability in the /segments/edit.php component of Domainmod 4.13 allows attackers to execute arbitrary web scripts or HTML via the Segment Name parameter. (2021-08-12, CVE-2020-20990)
In DomainMOD through 4.13, the parameter daterange in the file reporting/domains/cost-by-month.php has XSS. (2019-08-29, CVE-2019-15811)
DomainMOD version 4.09.03 and above. Also verified in the latest version 4.11.01 contains a Cross Site Scripting (XSS) vulnerability in Segment Name field in the segments page that can result in Arbitrary script can be executed on all users browsers who visit the affected page. This attack appear to be exploitable via Victim must visit the vulnerable page. This vulnerability appears to have been fixed in No fix yet. (2018-12-20, CVE-2018-1000856)
DomainMOD 4.11.01 has XSS via the assets/add/category.php Category Name or Stakeholder field. (2018-12-10, CVE-2018-20011)
DomainMOD 4.11.01 has XSS via the assets/add/ssl-provider-account.php username field. (2018-12-10, CVE-2018-20010)
DomainMOD 4.11.01 has XSS via the assets/add/ssl-provider.php SSL Provider Name or SSL Provider URL field. (2018-12-10, CVE-2018-20009)
DomainMOD through 4.11.01 has XSS via the assets/add/dns.php Profile Name or notes field. (2018-12-06, CVE-2018-19914)
DomainMOD through 4.11.01 has XSS via the assets/add/registrar-accounts.php UserName, Reseller ID, or notes field. (2018-12-06, CVE-2018-19913)
DomainMOD through 4.11.01 has XSS via the assets/edit/host.php Web Host Name or Web Host URL field. (2018-12-06, CVE-2018-19915)
DomainMOD through 4.11.01 has XSS via the admin/dw/add-server.php DisplayName, HostName, or UserName field. (2018-12-06, CVE-2018-19892)
DomainMOD through 4.11.01 has XSS via the admin/domain-fields/ notes field in an Add Custom Field action for Custom Domain Fields. (2018-11-29, CVE-2018-19750)
DomainMOD through 4.11.01 has XSS via the admin/ssl-fields/add.php notes field for Custom SSL Fields. (2018-11-29, CVE-2018-19751)
DomainMOD through 4.11.01 has XSS via the assets/add/account-owner.php Owner name field. (2018-11-29, CVE-2018-19749)
DomainMOD through 4.11.01 has XSS via the assets/add/registrar.php notes field for the Registrar. (2018-11-29, CVE-2018-19752)
DomainMOD through 4.11.01 has XSS via the assets/edit/ip-address.php ipid parameter. (2018-11-09, CVE-2018-19137)
DomainMOD through 4.11.01 has XSS via the assets/edit/registrar-account.php raid parameter. (2018-11-09, CVE-2018-19136)
DomainMod 4.10.0 has Stored XSS in the "/settings/profile/index.php" new_first_name parameter. (2018-05-30, CVE-2018-11558)
DomainMod 4.10.0 has Stored XSS in the "/settings/profile/index.php" new_last_name parameter. (2018-05-30, CVE-2018-11559)
DomainMod v4.09.03 has XSS via the assets/edit/account-owner.php oid parameter. (2018-05-24, CVE-2018-11403)
DomainMod v4.09.03 has XSS via the assets/edit/ssl-provider-account.php sslpaid parameter. (2018-05-24, CVE-2018-11404)
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>