dbcve.org
Document BuilderApplication · Sap

CVE-2024-39591

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
SAP Document Builder does not perform necessary authorization checks for one of the function modules resulting in escalation of privileges causing low impact on confidentiality 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 confidence

SAP Document Builder contains a missing authorization check vulnerability in one of its function modules, allowing unprivileged users to escalate their privileges. This leads to unauthorized access to functionality or data that should be restricted, with low impact on confidentiality.

MitigationImplement proper authorization checks on the affected function module in SAP Document Builder to ensure users can only access permitted functions based on their assigned roles and authorizations.

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
Document BuilderApplication
Affected:= s4fnd_102= s4fnd_103= s4fnd_104= s4fnd_105= s4fnd_106= s4fnd_107= s4fnd_108= sap_bs_fnd_702= sap_bs_fnd_731= sap_bs_fnd_746= sap_bs_fnd_747= sap_bs_fnd_748

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

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

  1. Verify SAP Document Builder is installed
    Access SAP transaction SE11 or SM37 to search for Document Builder related objects, or check SAP Software Lifecycle Manager (SLM) for installed software components matching Document Builder
    Affected if Document Builder component is present in the SAP system
  2. Identify installed Document Builder version
    Use SAP transaction SMAM (Software Component Monitor) or check the SAP System Landscape Directory (SLD) for the installed version of SAP Document Builder (look for component name containing 'Document Builder' or 'DOCBUILDER')
    Affected if Installed version matches s4fnd_102, s4fnd_103, s4fnd_104, s4fnd_105, s4fnd_106, s4fnd_107, s4fnd_108, sap_bs_fnd_702, sap_bs_fnd_731, sap_bs_fnd_746, sap_bs_fnd_747, or sap_bs_fnd_748
  3. Locate function modules in Document Builder
    Use SAP transaction SE37 (Function Builder) and search for function modules in the Document Builder namespace (typically under package SAP_DOCUMENT_BUILDER or related packages)
    Affected if Any function modules exist in the Document Builder package without documented authorization checks
  4. Review authorization objects assigned to function modules
    Use SAP transaction SE37 to display function module details, check the 'Attributes' tab for authorization objects, or use transaction SU53 after attempting to execute the function to see missing authorizations
    Affected if Function modules lack assigned authorization objects or return no authorization errors when called by unprivileged users
  5. Test for privilege escalation
    Using a test account with limited roles (no SAP_DOCUMENT_BUILDER_ADMIN or similar privileged roles), attempt to call Document Builder function modules via SE37 or RFC, and verify if access is granted when it should be denied
    Affected if Unprivileged users can successfully execute Document Builder functions that should require elevated privileges

A system is affected if SAP Document Builder is installed with a version matching the listed affected versions AND the vulnerable function module allows execution without proper authorization checks.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on the affected function module in SAP Document Builder to ensure users can only access permitted functions based on their assigned roles and authorizations.

Recommended fix Moderate confidence

Apply the SAP Security Note for CVE-2024-39591; the patch corrects the authorization check for the affected function module in Document Builder versions s4fnd_102 through s4fnd_105

  1. Check the SAP Security Note associated with CVE-2024-39591 on the SAP Support Portal (support.sap.com) to obtain the specific patch.
  2. Apply the SAP Security Patch via SAP Note Implementation Transaction (SNOTE) or maintenance optimizer.
  3. After applying the patch, verify that the authorization checks are now enforced for the affected function module in Document Builder.
  4. Test the Document Builder functionality to ensure the patch does not negatively impact existing workflows.
  5. Confirm that the privilege escalation vulnerability is remediated by attempting authorized and unauthorized operations.
Caveat Review SAP Security Note for any side effects or prerequisites before applying the patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Document Builder Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39591 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-39591 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