dbcve.org
Customer Relationship Management AbapApplication · Sap

CVE-2023-33986

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 CRM ABAP (Grantor Management) - versions 700, 701, 702, 712, 713, 714, does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability. After successful exploitation, an attacker can cause limited impact on confidentiality and integrity 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

Reflected Cross-Site Scripting (XSS) vulnerability in SAP CRM ABAP Grantor Management (versions 700-714). The application fails to properly encode user-controlled inputs, allowing attackers to inject malicious scripts into web pages viewed by other users.

MitigationApply SAP security patches for CVE-2023-33986. Until patches are applied, implement input validation and ensure proper output encoding is used for all user-supplied data in the Grantor Management component.

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
Customer Relationship Management AbapApplication
Affected:= 430

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Verify SAP CRM ABAP system is deployed
    Check if your SAP system runs SAP CRM ABAP by accessing SAP GUI and using transaction code SM51 (System Monitoring) or checking the system information via transaction SAINT (SAP Add-On Installation Tool). Look for 'SAP CRM' in the installed software components.
    Affected if Your system does not have SAP CRM ABAP installed - the vulnerability only applies to SAP CRM ABAP systems.
  2. Determine SAP CRM ABAP version
    In SAP GUI, execute transaction code SPAM (Support Package Manager) and navigate to 'Component Version' or use transactioncode SICF to check the SAP CRM component version. Alternatively, use transaction code SE16 and query table CVERS for component 'SAP_APPL' with release version in the 700-714 range.
    Affected if The installed SAP CRM ABAP version falls within range 700 to 714, indicating potential vulnerability.
  3. Confirm Grantor Management component is active
    Check if the Grantor Management component is accessible in your SAP CRM system. Use transaction code SE37 or search for function modules related to 'GRANTOR' using transaction code SE84 (Repository Info System) -> Enhancements -> Business Add-ins to verify if Grantor Management BAdIs are implemented.
    Affected if The Grantor Management component is active and user-accessible via web interfaces (via SAP CRM Web UI).
  4. Inspect web interface for unencoded output
    Access the Grantor Management web UI (typically via transaction code CRM_UI or WebUI). Use browser developer tools (F12) to inspect the HTTP response when submitting user input in Grantor Management fields. Look for reflected parameters in the URL query string that are echoed back in the HTML without proper encoding.
    Affected if User-supplied input appears in the URL or page source without HTML encoding (appearing as raw text or able to execute injected script tags).

You are affected if your SAP CRM ABAP system runs version 700-714 and has the Grantor Management web interface enabled with user-controllable input reflected in URLs or pages without encoding.

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 patches for CVE-2023-33986. Until patches are applied, implement input validation and ensure proper output encoding is used for all user-supplied data in the Grantor Management component.

Fix this in Customer Relationship Management Abap Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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