CVE-2019-4091
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited"HCL Marketing Platform is vulnerable to cross-site scripting during addition of new users and also while searching for users in Dashboard, potentially giving an attacker ability to inject malicious code into the system. "
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHCL Marketing Platform contains a cross-site scripting (XSS) vulnerability in the user addition and user search Dashboard functionalities. Attackers can inject malicious JavaScript code through these input fields, which executes in the browsers of other users who access the affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.1.0, < 10.1.0.4>= 11.1.0, < 11.1.0.3= 9.1.2.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed HCL Marketing Campaign versionLocate the product version information in the installation directory, typically in a version.txt file, or access the Marketing Platform's 'About' section in the admin consoleAffected if The installed version matches: 9.1.2.4, or falls in ranges >= 10.1.0 but < 10.1.0.4, or >= 11.1.0 but < 11.1.0.3
-
Confirm Marketing Platform Dashboard is accessibleAccess the HCL Marketing Platform administrative interface and navigate to the Dashboard sectionAffected if The Dashboard interface is accessible without additional security controls
-
Verify user addition functionality existsIn the Dashboard, locate the user creation or user addition form fieldsAffected if User addition input fields are present and accept user-supplied data
-
Verify user search functionality existsIn the Dashboard, locate the user search or user lookup featureAffected if User search input fields are present and accept user-supplied data
-
Test for input reflection in user fieldsEnter a benign test string such as '<script>alert(1)</script>' into the user creation and user search fields, then view the resulting page source or observe if the script executes in the browserAffected if The test string is reflected unescaped in the HTML output or the script executes
The environment is affected if the installed HCL Marketing Campaign version is 9.1.2.4 or falls within 10.1.0 to 10.1.0.3 or 11.1.0 to 11.1.0.2, AND the Dashboard user addition or user search functionalities are accessible and reflect input without proper encoding.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data10.1.0.411.1.0.3
Implement input validation and output encoding on all user-supplied input in the user creation and search functions. Apply context-appropriate sanitization and consider implementing Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-4091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-4091 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data