dbcve.org
OrocommerceApplication · Oroinc

CVE-2022-31037

MEDIUM · 5.4 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to after 5.0.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
OroCommerce is an open-source Business to Business Commerce application. Versions between 4.1.0 and 4.1.17 inclusive, 4.2.0 and 4.2.11 inclusive, and between 5.0.0 and 5.0.3 inclusive, are vulnerable to Cross-site Scripting in the UPS Surcharge field of the Shipping rule edit page. The attacker needs permission to create or edit a shipping rule. This issue has been patched in version 5.0.6. There are no known workarounds.

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

OroCommerce versions 4.1.0-4.1.17, 4.2.0-4.2.11, and 5.0.0-5.0.3 contain a stored Cross-site Scripting (XSS) vulnerability in the UPS Surcharge field of the Shipping rule edit page. An authenticated user with permissions to create or edit shipping rules can inject malicious JavaScript into the UPS Surcharge input field, which executes when other users view the affected shipping rule configuration.

MitigationUpgrade to OroCommerce version 5.0.6 or later which contains the security patch. There are no known workarounds; patching is the only remediation option.

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
OrocommerceApplication
Affected:>= 4.1.0, <= 4.1.17>= 4.2.0, <= 4.2.11>= 5.0.0, <= 5.0.3

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed OroCommerce version
    Locate the version file or admin panel (typically at /admin/oro/version or in composer.json) and note the exact version number
    Affected if version falls within 4.1.0-4.1.17, 4.2.0-4.2.11, or 5.0.0-5.0.3
  2. Verify user has shipping rule permissions
    Check if your user role includes permissions to create or edit shipping rules (Commerce > Shipping > Shipping Rules)
    Affected if you have or can obtain permissions to access shipping rule configuration
  3. Confirm UPS shipping method is configured
    Navigate to System > Configuration > Shipping Methods and verify UPS is enabled or has been set up in the environment
    Affected if UPS shipping method is present or was previously configured
  4. Inspect shipping rules for UPS Surcharge field
    Go to Commerce > Shipping > Shipping Rules, open any existing rule, and look for the UPS Surcharge input field in the shipping rule edit page
    Affected if the UPS Surcharge field exists and accepts input without sanitization

You are affected if your OroCommerce version is within the vulnerable range AND you have shipping rule management permissions AND UPS shipping is configured, as the stored XSS can be injected into the UPS Surcharge field.

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

Upgrade to OroCommerce version 5.0.6 or later which contains the security patch. There are no known workarounds; patching is the only remediation option.

Recommended fix High confidence

5.0.6 or later (5.1.x recommended)

  1. 1. Backup your current OroCommerce database and files.
  2. 2. Review the OroCommerce upgrade documentation for your current version.
  3. 3. Upgrade to version 5.0.6 or later (5.1.x if available).
  4. 4. Verify the upgrade was successful by logging into the admin panel.
  5. 5. Test that the Shipping Rules functionality works correctly with the UPS Surcharge field.
  6. 6. Confirm the patch is applied by checking the UPS Surcharge field no longer accepts unsanitized input.
Caveat Upgrading from 4.x to 5.x involves significant changes; review the OroCommerce migration guide for breaking changes between 4.x and 5.x

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

Fix this in Orocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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