dbcve.org
Commerce Service CenterApplication · Oracle

CVE-2021-2462

MEDIUM · 6.1 CVSS v3.1 Published 2021-07-21
Fix available
A fix is available. Upgrade to after 11.3.2 or later.
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
Vulnerability in the Oracle Commerce Service Center product of Oracle Commerce (component: Commerce Service Center). Supported versions that are affected are 11.0.0, 11.1.0, 11.2.0 and 11.3.0-11.3.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Commerce Service Center. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Commerce Service Center, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Commerce Service Center accessible data as well as unauthorized read access to a subset of Oracle Commerce Service Center accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

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

Unauthenticated attacker can exploit Oracle Commerce Service Center via HTTP to achieve unauthorized read and delete access to a subset of data. The vulnerability requires human interaction (likely a phishing or social engineering component), indicating a potential Cross-Site Scripting (XSS) or similar injection flaw in the web interface.

MitigationApply Oracle's patches for this vulnerability or upgrade to a patched version of Oracle Commerce. If patches are unavailable, implement input validation, output encoding, and consider restricting network access to the Commerce Service Center until a fix is applied.

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
Commerce Service CenterApplication
Affected:>= 11.3.0, <= 11.3.2= 11.0.0= 11.1.0= 11.2.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
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. Identify Oracle Commerce Service Center version
    Locate the Oracle Commerce installation directory and check the version file or use the Oracle Commerce admin interface to view version information. Common locations include the installation logs or version manifest files within the Commerce platform directories.
    Affected if The installed version matches 11.0.0, 11.1.0, 11.2.0, or falls between 11.3.0 and 11.3.2 inclusive.
  2. Confirm Service Center web interface is exposed
    Determine if the Oracle Commerce Service Center application is accessible over HTTP/HTTPS from the network. Check the web server configuration or reverse proxy settings that expose the Service Center endpoint.
    Affected if The Service Center web interface is accessible externally or to untrusted networks without proper access controls.
  3. Verify authentication mechanisms for Service Center
    Review the Oracle Commerce authentication configuration files and web.xml to confirm whether authentication is properly enforced on the Service Center endpoints.
    Affected if Authentication is disabled, weakened, or bypassed for the Service Center application paths.
  4. Inspect for existing injection points or XSS vectors
    Review application logs and input validation configurations in the Commerce platform to identify any unvalidated input fields or potential injection points in the Service Center.
    Affected if Input validation is minimal or absent, allowing unsanitized user input in Service Center requests.

A user is affected if Oracle Commerce Service Center is running an affected version (11.0.0, 11.1.0, 11.2.0, or 11.3.0-11.3.2) and the web interface is network-accessible to unauthenticated users.

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
Upgrade available Upgrade to a release after 11.3.2
Interim mitigation

Apply Oracle's patches for this vulnerability or upgrade to a patched version of Oracle Commerce. If patches are unavailable, implement input validation, output encoding, and consider restricting network access to the Commerce Service Center until a fix is applied.

Fix this in Commerce Service Center Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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