CVE-2023-39437
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 allows - version 10.0, allows an attacker to insert malicious code into the content of a web page or application and gets it delivered to the client, resulting to Cross-site scripting. This could lead to harmful action affecting the Confidentiality, Integrity and Availability of the application.
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 confidenceSAP Business One version 10.0 contains a stored Cross-site scripting (XSS) vulnerability where an attacker can inject malicious script content into application pages. When other users view the compromised content, the injected JavaScript executes in their browsers, potentially allowing session hijacking, credential theft, or actions on behalf of the victim.
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.0CVSS 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 SAP Business One installed versionAccess SAP Business One Administration Console or check the program's version information through Help > About SAP Business One in the client interfaceAffected if The installed version is exactly 10.0 (no patches applied)
-
Confirm the web component is accessibleDetermine if the SAP Business One web browser access or any web-based interface component is enabled and accessible to usersAffected if Web-based access is enabled and users can interact with application pages through a browser interface
-
Identify user input fields in web pagesReview SAP Business One web application pages and identify fields where user-supplied content is stored and rendered back to other users (such as comments, notes, description fields, or custom fields)Affected if Any input fields accept and store content that gets displayed to other users without proper encoding
-
Test for stored XSS in input fieldsUsing an authorized test account, attempt to inject a benign script tag (such as <script>alert('test')</script>) into known user input fields and then view the stored content from a different user sessionAffected if The injected script executes when viewed by another user, confirming stored XSS vulnerability
-
Check for existing script injectionsSearch application databases or logs for suspicious script tags, event handlers, or encoded JavaScript patterns in data fields that may indicate prior exploitationAffected if Malicious script content is found stored in application databases or being rendered in pages
A user is affected if they are running SAP Business One version 10.0 with web-based interface access enabled and have user input fields that render stored content without 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 dataApply SAP security patches when available; implement proper input validation and output encoding/sanitization for all user-supplied content rendered in web pages.
- 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-2023-39437 — 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-2023-39437 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