CVE-2018-2410
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 · uneditedSAP Business One, 9.2, 9.3, browser access does not sufficiently encode user controlled inputs, which results in a Cross-Site Scripting (XSS) vulnerability.
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 confidenceSAP Business One versions 9.2 and 9.3 contain a Cross-Site Scripting (XSS) vulnerability in the browser access component. User-controlled inputs are not sufficiently encoded, allowing attackers to inject malicious scripts that execute in the context of other users' sessions.
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= 9.2= 9.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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 SAP Business One versionOpen the SAP Business One client, go to Help > About SAP Business One, or check the version in the License Manager. Alternatively, query the SBO_SP_TransactionNotification stored procedure or check the System Landscape Directory for installed version information.Affected if The installed version is exactly 9.2 or exactly 9.3.
-
Confirm browser access component is enabledCheck if the SAP Business One web browser access / web client feature is installed and active. This is typically configured in the SAP Business One Server Manager under Web Client or Browser Access settings, or by attempting to access the web interface URL (commonly port 8080 or 443).Affected if The browser access component is enabled and reachable via HTTP/HTTPS.
-
Locate the web login or input formsAccess the SAP Business One web portal URL and navigate to login fields or any user-input forms such as username, password, or search fields. These are the entry points where unsanitized input could be exploited.Affected if The web interface exposes input fields that accept user-controlled data without visible output encoding.
-
Inspect for lack of input sanitization (optional manual test)View the page source or use browser developer tools to inspect whether user inputs are being rendered back without proper HTML encoding. Look for <script> tags or event handlers in the response when test input is submitted.Affected if User input appears unencoded in the HTML response (e.g., < becomes < is NOT present).
You are affected if SAP Business One version 9.2 or 9.3 is installed AND the browser access component is enabled and handles user input without output 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 dataApply the relevant SAP security patch for CVE-2018-2410 and implement output encoding for all user-controlled inputs in the affected web interfaces.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.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,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2410 — 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-2410 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