LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25104: CoinGate Plugin Payment callback.php postProcess logic error

A vulnerability was found in CoinGate Plugin up to 1.2.7 on PrestaShop. It has been rated as problematic. Affected by this issue is the function postProcess of the file modules/coingate/controllers/front/callback.php of the component Payment Handler. The manipulation leads to business logic errors. The attack may be launched remotely. Upgrading to version 1.2.8 is able to address this issue. The patch is identified as 0a3097db0aec7c5d66686c142c6abaa1e126ca16. It is recommended to upgrade the affected component.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-25104 affects the CoinGate payment plugin for PrestaShop. A logic flaw in the payment callback handler could allow improper payment-state handling, creating business risk around order processing. The issue is rated medium and is fixed in CoinGate Plugin 1.2.8.

Executive priority

Treat this as a targeted e-commerce integrity issue, not an emergency internet-wide compromise. Prioritize upgrades for stores using CoinGate payments, because incorrect callback handling can affect revenue, fulfillment, and customer trust even without system takeover.

Technical view

The flaw is in postProcess within modules/coingate/controllers/front/callback.php, classified as CWE-840 business logic error. The CVSS 4.0 vector shows network attackability, low attack complexity, low privileges required, no user interaction, and low integrity impact. Versions 1.2.0 through 1.2.7 are listed as affected.

Likely exposure

Exposure is likely limited to PrestaShop sites running CoinGate Plugin versions 1.2.0 through 1.2.7, especially stores actively using CoinGate payment callbacks for order handling.

Exploitation context

The source bundle states remote attack is possible, but privileges are required. CISA KEV is false, and the provided sources do not state active exploitation, public exploit availability, or observed attacks.

Researcher notes

Evidence is concise and centered on VulDB, CVE records, and the upstream patch/release. The bundle does not describe exact exploit mechanics, affected PrestaShop versions, or compensating controls. Validation should focus on version exposure and business workflow integrity rather than host compromise indicators.

Mitigation direction

  • Upgrade CoinGate Plugin to version 1.2.8 or later.
  • Confirm the deployed plugin includes patch commit 0a3097db0aec7c5d66686c142c6abaa1e126ca16.
  • Review CoinGate and PrestaShop vendor guidance before production rollout.
  • Monitor payment and order-status records for unusual callback-driven state changes.

Validation and detection

  • Inventory PrestaShop instances for the CoinGate Plugin and installed version.
  • Confirm no production site runs CoinGate Plugin 1.2.0 through 1.2.7.
  • Validate payment callback behavior in staging after upgrading.
  • Review recent order histories for inconsistent payment or fulfillment states.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-840: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-25104 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.3Medium
CVSS 4.0 vector shape for CVE-2018-25104Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aCoinGate Plugin1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-840 · source CWE mapping

Business Logic Errors

Business Logic Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.