CVE-2019-18943
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 · uneditedMicro Focus Solutions Business Manager versions prior to 11.7.1 are vulnerable to XML External Entity Processing (XXE) on certain operations.
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 confidenceMicro Focus Solutions Business Manager versions prior to 11.7.1 contain XML External Entity (XXE) injection vulnerabilities in certain operations. The application parses XML input without properly disabling external entity processing, potentially allowing authenticated attackers to read local files, perform server-side request forgery (SSRF), or cause denial of service.
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< 11.7.1CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 versionLocate the Solutions Business Manager version information in the application's About page, version file, or installation directory documentation. Common locations include the admin interface, installation logs, or product documentation.Affected if The installed version is any release prior to 11.7.1 (for example, 11.6.x, 11.5.x, or earlier releases).
-
Verify application accessibilityConfirm that the Solutions Business Manager web interface or API endpoints are reachable and user authentication is configured.Affected if The application is exposed online or on an accessible network without proper access controls, allowing authenticated users to submit XML-based requests.
-
Identify XML parsing operationsReview the application's available operations, particularly those involving XML input such as data imports, configuration uploads, report definitions, or integration endpoints.Affected if XML-based operations are accessible to authenticated users and accept XML payloads without visible evidence of XML entity processing being disabled.
-
Check XML parser configurationIf you have access to application configuration files or XML processor settings, inspect them for external entity (DTD or entity) processing configuration.Affected if The XML parser is configured to allow external entity resolution or DTD processing is not explicitly disabled.
You are affected if your installed Solutions Business Manager version is below 11.7.1 AND the application exposes XML parsing operations to authenticated users without proper entity processing restrictions.
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 data11.7.1
Upgrade to Solutions Business Manager version 11.7.1 or later. If immediate upgrade is not feasible, disable external entity processing in the application's XML parser configuration as a temporary workaround.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18943 — 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-18943 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