dbcve.org
InjectionWeakness · CWE-74

CVE-2025-0579

HIGH · 7.3 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 →
82/100
Remediation priority · High
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/4 on OpenCart. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /index.php?route=extension/shiprocket/module/restapi of the component REST API Module. The manipulation of the argument x-username leads to sql injection. The attack can be launched remotely. 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 · high confidence

SQL injection vulnerability in Shiprocket Module 3/4 for OpenCart REST API endpoint (/index.php?route=extension/shiprocket/module/restapi). The x-username parameter is not properly sanitized before use in SQL queries, allowing remote attackers to inject malicious SQL code. Public exploit available, and vendor did not respond to early disclosure.

MitigationImplement parameterized queries/prepared statements for all database operations using the x-username parameter, add input validation and sanitization, and apply a WAF rule as temporary mitigation until the code fix is deployed.

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

CVSS:3.1/AV:N/AC:L/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. Confirm OpenCart installation
    Look for OpenCart installation by checking for the presence of /admin/index.php and /catalog/index.php, or check your web root for opencart directories.
    Affected if OpenCart is installed on the server
  2. Identify Shiprocket module presence
    Check for the Shiprocket module directory at /admin/controller/extension/shiprocket/ and /catalog/controller/extension/shiprocket/, or list files containing 'shiprocket' in the extension directories.
    Affected if Shiprocket Module 3 or 4 for OpenCart is installed
  3. Determine Shiprocket module version
    Review the Shiprocket module's main controller file (usually controller/module/restapi.php or similar) for a version variable, or check the module's XML installation file in /system/ for version metadata.
    Affected if The installed version matches Shiprocket Module 3 or 4 and has not been patched
  4. Verify REST API endpoint is exposed
    Attempt to access /index.php?route=extension/shiprocket/module/restapi via HTTP request and confirm the endpoint responds (even with an authentication error).
    Affected if The endpoint returns any response indicating it exists and is reachable
  5. Confirm vulnerable parameter handling
    Review the REST API controller code in the Shiprocket module for the x-username header parameter usage. Search for SQL query construction that incorporates $this->request->get['x-username'] or $_SERVER['HTTP_X_USERNAME'] without prepared statements or escaping.
    Affected if The code uses the x-username parameter directly in SQL queries without sanitization

User is affected if OpenCart with Shiprocket Module 3 or 4 is installed, the REST API endpoint is accessible, and the module code contains direct SQL query construction using the x-username parameter without parameterized 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 parameterized queries/prepared statements for all database operations using the x-username parameter, add input validation and sanitization, and apply a WAF rule as temporary mitigation until the code fix is deployed.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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