dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-0580

MEDIUM · 5.6 CVSS v3.1 Published 2025-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/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
A vulnerability was found in Shiprocket Module 3 on OpenCart. It has been rated as critical. Affected by this issue is some unknown functionality of the file /index.php?route=extension/module/rest_api&action=getOrders of the component REST API Module. The manipulation of the argument contentHash leads to incorrect authorization. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

The Shiprocket Module 3 for OpenCart contains an incorrect authorization vulnerability in its REST API endpoint at /index.php?route=extension/module/rest_api&action=getOrders. The contentHash argument is not properly validating user authorization, allowing attackers to potentially access order data without proper authentication. This is a remote authorization bypass with high attack complexity.

MitigationDisable the Shiprocket REST API module until an official patch is released, or implement additional authentication controls at the web server/application level to restrict unauthorized access to the getOrders endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

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 OpenCart installation
    Check for the presence of OpenCart by looking for admin/index.php and catalog/controller/ directories, or check for op2023 or similar session cookies
    Affected if OpenCart is installed and running
  2. Confirm Shiprocket Module 3 is installed
    Look for the Shiprocket module files in admin/controller/extension/module/shiprocket.php or catalog/controller/extension/module/shiprocket.php, or check in the OpenCart admin under Extensions > Modules for Shiprocket
    Affected if The Shiprocket module appears in the installed extensions list
  3. Check Shiprocket module version
    Open the main Shiprocket module file and look for a version constant or check the admin panel module details page for the installed version number
    Affected if The installed version falls within the vulnerable version range and has not been patched
  4. Verify REST API module is enabled
    In OpenCart admin, go to Extensions > Modules and check if the Shiprocket REST API or related API module is enabled, or check the module configuration in the database under the setting table
    Affected if The REST API functionality is enabled in the Shiprocket module configuration
  5. Confirm endpoint accessibility
    Attempt to access /index.php?route=extension/module/rest_api&action=getOrders without valid authentication headers and observe if the request is processed rather than rejected
    Affected if The endpoint accepts requests without proper authorization validation

A user is affected if they have Shiprocket Module 3 for OpenCart installed with the REST API enabled and the vulnerable version is in use, allowing unauthenticated access to the getOrders endpoint.

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

Disable the Shiprocket REST API module until an official patch is released, or implement additional authentication controls at the web server/application level to restrict unauthorized access to the getOrders endpoint.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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