CVE-2019-11676
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 · uneditedThe user defined DNS name in Zoho ManageEngine Firewall Analyzer before 12.3 Build 123224 is vulnerable to stored XSS attacks.
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 confidenceZoho ManageEngine Firewall Analyzer versions before 12.3 Build 123224 contain a stored cross-site scripting (XSS) vulnerability in the user-defined DNS name field. Attackers can inject malicious JavaScript that persists in the application and executes when other users access the DNS name configuration, potentially stealing session cookies or performing actions on behalf of authenticated users.
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= 7.2= 7.4= 7.6= 8.0= 8.1= 8.3= 8.5= 12.0= 12.2= 12.3CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 Firewall Analyzer versionLocate the application version. Common paths include: checking the product GUI under 'Help > About', the installation directory readme or version file, or the admin console login page which often displays the build number.Affected if The installed version matches any of these: 7.2, 7.4, 7.6, 8.0, 8.1, 8.3, 8.5, 12.0, 12.2, or 12.3 (any build before 123224)
-
Confirm build number is before 123224Locate the specific build number in the application. In the web interface, this is often visible on the login page or in the admin dashboard under 'Product Information'. Compare it to the fixed version: Build 123224.Affected if The build number is lower than 123224, meaning the security patch has not been applied
-
Locate DNS name configurationAccess the DNS name setting in the application. This is typically found in: Admin > Network Settings > DNS Configuration, or Settings > Network > DNS Name. The exact path varies by build.Affected if You can access and view the DNS name configuration field in the application interface
-
Inspect DNS name field for script tagsView the current DNS name value. Check for any unexpected characters such as <script>, javascript:, onload, onerror, or other HTML/script injections in the DNS name field.Affected if The DNS name field contains any HTML, JavaScript, or encoded script content that was not entered by an administrator
You are affected if your installed version is any of 7.2, 7.4, 7.6, 8.0, 8.1, 8.3, 8.5, 12.0, 12.2, or 12.3 (build below 123224) and the DNS name field contains injected script content.
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 dataUpgrade ManageEngine Firewall Analyzer to version 12.3 Build 123224 or later to obtain the vendor patch that addresses the XSS vulnerability in the DNS name field.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11676 — 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-11676 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