dbcve.org
InjectionWeakness · CWE-74

CVE-2025-1117

HIGH · 7.3 CVSS v3.1 Published 2025-02-08
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, which was classified as critical, was found in CoinRemitter 0.0.1/0.0.2 on OpenCart. This affects an unknown part. The manipulation of the argument coin leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 0.0.3 is able to address this issue. It is recommended to upgrade the affected component.

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

SQL injection vulnerability in the CoinRemitter payment plugin for OpenCart allows remote attackers to inject malicious SQL queries via the 'coin' parameter. The vulnerability affects versions 0.0.1 and 0.0.2, and exploitation requires no authentication. Upgrading to version 0.0.3 patches the vulnerable code.

MitigationImmediately upgrade the CoinRemitter plugin from version 0.0.1/0.0.2 to version 0.0.3 to remediate the SQL injection. If immediate upgrade is not possible, consider temporarily disabling the CoinRemitter payment module.

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. Locate CoinRemitter plugin files in OpenCart installation
    Search for files containing 'coinremitter' in the OpenCart directory structure, typically under admin/controller/extension/payment/ or catalog/controller/extension/payment/
    Affected if CoinRemitter plugin files exist in the OpenCart installation
  2. Determine installed CoinRemitter plugin version
    Open the main CoinRemitter controller file and locate the version identifier, often declared as a constant or variable at the top of the file
    Affected if Installed version is 0.0.1 or 0.0.2
  3. Verify CoinRemitter payment module is enabled
    Log into OpenCart admin panel and navigate to Extensions > Payments, or query the oc_extension table in the database to check if the coinremitter module status is 'enabled'
    Affected if The CoinRemitter payment module is installed and enabled in OpenCart
  4. Confirm vulnerable parameter handling exists
    Examine the CoinRemitter controller file for the 'coin' parameter handling, specifically looking for direct use of this parameter in database queries without proper sanitization
    Affected if The code processes the 'coin' parameter in SQL queries without prepared statements or escaping

User is affected if CoinRemitter plugin versions 0.0.1 or 0.0.2 are installed and the payment module is enabled in OpenCart.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately upgrade the CoinRemitter plugin from version 0.0.1/0.0.2 to version 0.0.3 to remediate the SQL injection. If immediate upgrade is not possible, consider temporarily disabling the CoinRemitter payment module.

Recommended fix High confidence

CoinRemitter 0.0.3

  1. Identify the CoinRemitter extension version currently installed on your OpenCart site
  2. Backup your OpenCart database and files before performing any upgrade
  3. Download CoinRemitter version 0.0.3 from the official source or marketplace
  4. Upload and install the CoinRemitter 0.0.3 extension to your OpenCart installation
  5. Clear any caches (OpenCart cache, system cache, theme cache) after installation
  6. Verify the extension is functioning correctly by testing the payment workflow
  7. Confirm the SQL injection vulnerability is resolved by checking that the 'coin' parameter is properly sanitized
Caveat Review OpenCart compatibility for version 0.0.3 before upgrading; ensure your OpenCart version supports the new extension version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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