Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2018-19913: XSS in DomainMOD registrar-accounts.php

Published Dec 6, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.8Medium · v3
EPSS1.8%79th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Domainmod
IdentifiersCVE-2018-19913CWE-79 · Improper Neutralization of Input…

DomainMOD through version 4.11.01 is vulnerable to cross-site scripting (XSS) in the assets/add/registrar-accounts.php script. The vulnerability is present in the handling of the UserName, Reseller ID, or notes fields, which do not properly sanitize user-supplied input, allowing for the injection of arbitrary JavaScript code.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can exploit this XSS vulnerability to execute arbitrary JavaScript in the context of the victim's browser session. This can lead to session hijacking, credential theft, or other malicious actions performed on behalf of the victim within the DomainMOD application.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, restrict access to the registrar-accounts.php page to trusted users only. Employ web application firewalls (WAFs) with XSS filtering, and ensure that input validation and output encoding are enforced for all user-supplied fields.

Remediation

Patch, then assume compromise.

Upgrade DomainMOD to a version after 4.11.01 where this vulnerability is patched. Ensure that all user-supplied input in registrar-accounts.php is properly sanitized and output is correctly encoded to prevent XSS.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DomainmodDomainmodapplication
FAQ

Frequently asked questions

Is CVE-2018-19913 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2018-19913 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2018-19913?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2018-19913.
Is there a patch for CVE-2018-19913?
Upgrade DomainMOD to a version after 4.11.01 where this vulnerability is patched. Ensure that all user-supplied input in registrar-accounts.php is properly sanitized and output is correctly encoded to prevent XSS.
What products are affected by CVE-2018-19913?
Domainmod.
How severe is CVE-2018-19913?
CVE-2018-19913 has a CVSS v3 score of 4.8 (Medium) and an EPSS score of 1.8% (79th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.