CVE-2022-31593
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 client - version 10.0 allows an attacker with low privileges, to inject code that can be executed by the application. An attacker could thereby control the behavior 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 confidenceCode injection vulnerability in SAP Business One client version 10.0 allows an authenticated attacker with low privileges to inject malicious code that gets executed by the application, enabling control of application behavior. The high CVSS score (8.8) indicates significant impact on confidentiality, integrity, and availability.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Verify SAP Business One client versionOpen SAP Business One client application, go to Help > About SAP Business One, or check the installed version via the Windows Programs and Features (Add/Remove Programs) panel. Look for the exact version number displayed.Affected if The installed version is exactly 10.0 (version 10.0, no patch level specified in the advisory)
-
Confirm user account privilege levelLog into the SAP Business One client with the account in question. Navigate to Administration > System Initialization > Authorizations > Authorization Templates, or check the user's role assignment through the User Master Data to determine their privilege level.Affected if The attacker account has low privileges (authenticated with basic/user-level access rather than full administrative rights)
-
Inspect client-side customization filesCheck the SAP Business One client installation directory (typically under C:\Program Files\SAP\SAP Business One\) for any unexpected .dll, .b1f, or script files added after the installation date. Also check the \CustomCode\ folder if present.Affected if Unknown or unauthorized DLL files, B1F forms, or custom scripts exist in the client directories that were not deployed by your administration team
-
Review application logs for code executionAccess SAP Business One logs located in the user's local AppData folder (typically C:\Users\<username>\AppData\Local\SAP\SAP Business One\Logs\) or server logs. Search for entries indicating execution of custom code, script invocations, or unusual process spawns.Affected if Logs show execution of unfamiliar scripts, custom procedures, or code that was not explicitly authorized by your administration team
You are affected if the SAP Business One client version is exactly 10.0 AND an authenticated low-privilege user account can inject and execute arbitrary code within the application context.
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 vendor patch from SAP for Business One 10.0; implement strict input validation on all client-side inputs; review and enforce least-privilege user roles to limit injection impact.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31593 — 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-2022-31593 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