Business OneApplication · Sap

CVE-2023-33993

HIGH · 7.5 CVSS v3.1 Published 2023-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
B1i module of SAP Business One - version 10.0, application allows an authenticated user with deep knowledge to send crafted queries over the network to read or modify the SQL data. On successful exploitation, the attacker can cause high impact on 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 · high confidence

SQL injection vulnerability in the B1i module of SAP Business One version 10.0 allows authenticated users with specialized knowledge to send crafted queries over the network to read or modify SQL database data, impacting confidentiality, integrity, and availability.

MitigationApply SAP Security Note addressing CVE-2023-33993; restrict B1i module network access to authorized personnel only; verify all B1i user accounts follow least-privilege principles.

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
Business OneApplication
Affected:= 10.0

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP Business One installed version
    Check the SAP Business One version installed in your environment using the SAP Business One Control Center, version information in the SAP Business One client, or system information in SAP B1 Service Manager. Compare this version number against the affected version 10.0.
    Affected if The installed version is exactly 10.0 (version 10.0, no patch level specified)
  2. Verify B1i module is enabled
    Check the SAP Business One B1i configuration settings. The B1i (Business One Integration) module is typically configured in the SAP Business One Integration Server settings, found in the Integration Tools section of the SAP Business One Administrator console or via the B1i Service configuration panel.
    Affected if The B1i module is installed and enabled in the SAP Business One environment
  3. Confirm B1i network exposure
    Review network configuration and firewall rules for the B1i service port. B1i typically exposes HTTP/HTTPS endpoints for integration. Check if the B1i service is reachable over the network from systems other than the local server.
    Affected if The B1i module is network-accessible beyond the local server or from untrusted networks
  4. Review B1i user accounts and privileges
    Check the user accounts configured for B1i module access in SAP Business One. Access the user management section in SAP Business One Administrator and review which users have B1i-related permissions or are assigned to B1i integration roles.
    Affected if B1i user accounts exist with elevated database access privileges or permissions beyond what is required for their specific integration function

You are affected if your SAP Business One installation is version 10.0, the B1i module is enabled, and it is network-accessible to users with B1i credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP Security Note addressing CVE-2023-33993; restrict B1i module network access to authorized personnel only; verify all B1i user accounts follow least-privilege principles.

Fix this in Business One Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33993 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-33993 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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