dbcve.org
CommerceApplication · Sap

CVE-2021-27619

MEDIUM · 6.5 CVSS v3.1 Published 2021-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
SAP Commerce (Backoffice Search), versions - 1808, 1811, 1905, 2005, 2011, allows a low privileged user to search for attributes which are not supposed to be displayed to them. Although the search results are masked, the user can iteratively enter one character at a time to search and determine the masked attribute value thereby leading to information disclosure.

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 Commerce Backoffice Search has an information disclosure vulnerability where low-privileged users can discover masked attribute values by performing iterative character-by-character searches. Although the system masks certain attributes from unauthorized users, the masking can be bypassed through brute-force enumeration—users enter one character at a time to progressively determine the actual attribute values, bypassing intended access controls.

MitigationImplement proper server-side enforcement of attribute-level access controls and rate-limit or block iterative search patterns that could be used for enumeration. Consider adding account lockouts or CAPTCHA after failed search attempts and ensure authorization checks occur before returning any attribute data.

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
CommerceApplication
Affected:= 1808= 1811= 1905= 2005= 2011

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify SAP Commerce version
    Locate the SAP Commerce installation and retrieve the exact version number. This is typically found in the platform installer, manifest files, or the admin console under system information.
    Affected if The installed version matches 1808, 1811, 1905, 2005, or 2011 exactly.
  2. Confirm Backoffice module is deployed
    Verify that the SAP Commerce Backoffice module is installed and accessible in the environment. Check the backend configuration or module list.
    Affected if Backoffice is deployed and accessible to users.
  3. Check if search functionality is accessible to low-privileged users
    Review user role assignments and permissions to determine whether standard or low-privileged users have access to the Backoffice search feature. Inspect the backoffice-config.xml or equivalent role definition files.
    Affected if Users with limited privileges can access and use the Backoffice search functionality.
  4. Identify if masked attributes are configured in Backoffice
    Examine the Backoffice configuration for attributes that have masking or field-level security applied. Look for attributes marked as sensitive in the backoffice item types configuration.
    Affected if The Backoffice search exposes any attributes that are configured with masking or restricted display rules.
  5. Inspect search query behavior for enumeration patterns
    Test the search functionality with iterative single-character queries to observe if the system returns different result sets that could reveal character-by-character information about masked values.
    Affected if The search returns distinct results that allow progressive character-by-character deduction of masked attribute values.

A user is affected if running SAP Commerce version 1808, 1811, 1905, 2005, or 2011 with Backoffice search accessible to low-privileged users who can enumerate masked attribute values through iterative search queries.

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

Implement proper server-side enforcement of attribute-level access controls and rate-limit or block iterative search patterns that could be used for enumeration. Consider adding account lockouts or CAPTCHA after failed search attempts and ensure authorization checks occur before returning any attribute data.

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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