Security readout for executives and security teams
Plain-English summary
DomainMOD through 4.11.01 is reported to allow cross-site scripting in the Owner name field when adding an account owner. A malicious value could run script in another user's browser if the affected page displays it unsafely. Business impact depends on who can access DomainMOD and what privileges their session has.
Executive priority
Prioritize if DomainMOD manages business-critical domains or is used by multiple administrators. The issue is public and affects an administrative workflow, but urgency is constrained by missing severity data and no cited active exploitation.
Technical view
The CVE describes XSS in assets/add/account-owner.php through the Owner name field. Public references include a GitHub issue and an Exploit-DB entry, but the bundle provides no CVSS score, CWE, authentication context, fixed version, or vendor-confirmed remediation details.
Likely exposure
Exposure is limited to organizations running DomainMOD through 4.11.01, especially where the account-owner add workflow is reachable by multiple users. Internet exposure is not established by the provided sources.
Exploitation context
A public exploit reference exists, but CISA KEV status is false and the provided sources do not show active exploitation in the wild. Treat this as publicly known and reproducible, not confirmed actively exploited.
Researcher notes
The source bundle lacks CVSS, CWE, patch status, and authentication requirements. Analysis should verify DomainMOD version, page reachability, role requirements, and whether stored or reflected rendering occurs before assigning a final operational risk.
Mitigation direction
- Identify whether DomainMOD is deployed and its exact version.
- Check DomainMOD upstream guidance for a fixed release or official patch.
- Restrict DomainMOD access to trusted administrative users until remediated.
- Review compensating controls such as input filtering and browser-side script restrictions.
Validation and detection
- Confirm whether assets/add/account-owner.php exists in deployed instances.
- Check whether the Owner name field is reachable by untrusted users.
- Review records and logs for suspicious Owner name values containing markup or script indicators.
- Verify remediation against vendor guidance without using production exploit attempts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-19749 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/domainmod/domainmod/issues/81CVE reference · x_refsource_MISC
- 45941CVE reference · exploit, x_refsource_EXPLOIT-DB
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.