CVE-2018-7680
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.4 can reflect back HTTP header values.
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 · moderate confidenceMicro Focus Solutions Business Manager versions prior to 11.4 contain an HTTP header injection vulnerability where the application reflects user-supplied HTTP header values back in responses without proper sanitization. This can allow attackers to inject malicious headers, potentially leading to HTTP response splitting, cross-site scripting, or cache poisoning attacks.
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.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
- 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.
-
Check Solutions Business Manager version via web interfaceAccess the application login page or main dashboard and look for version information typically found in the Help, About, or System Info section. This is often accessible via a menu option or by appending /about, /info, or /version to the application URL.Affected if The displayed version is a number lower than 11.4 or the version information shows no version number or is unknown (older unpatched versions may not display version info)
-
Check version via administrator console or system settingsLog in to the administrative console or system settings panel of the application and locate the product information or system status page, which commonly displays the installed software version.Affected if The version shown is below 11.4
-
Check version in application logs or configuration filesExamine server logs, installation logs, or configuration files within the application installation directory for version strings. Common locations include logs/system.log, version.txt, or the main configuration file.Affected if Any discovered version reference indicates a build or version number less than 11.4
-
Identify if the application processes and reflects custom HTTP headersSend a test HTTP request to the application with a custom header (for example, X-Test-Header: testvalue) and examine the response headers and body to see if the value is reflected back without sanitization. This typically requires web traffic inspection tools.Affected if The application returns the custom header value in responses without encoding or validation, which combined with version < 11.4 confirms the vulnerability is present
A system is affected if Micro Focus Solutions Business Manager is installed with any version number below 11.4, as prior versions reflect user-supplied HTTP header values without proper sanitization.
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.4
Upgrade to Solutions Business Manager version 11.4 or later. Additionally, implement input validation and output encoding for all HTTP header values to prevent injection attacks.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7680 — 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-2018-7680 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