LiveActive security incident?Get immediate response
CVE Record

CVE-2018-13328: The transfer, transferFrom, and mint functions of a smart contract implementation for PFGc, an Ethereum tok...

The transfer, transferFrom, and mint functions of a smart contract implementation for PFGc, an Ethereum token, have an integer overflow.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-13328 concerns an Ethereum token contract for PFGc. Its token transfer and minting functions reportedly allow integer overflow, which can corrupt balances or token supply. The public record does not provide severity, affected deployment details, or a confirmed fix.

Executive priority

Treat this as an exposure-discovery item, not an emergency confirmed incident. Prioritize validation if the organization holds PFGc, lists it, integrates it, or forked its code. Business urgency rises if real funds, customer balances, or automated workflows depend on the contract.

Technical view

The CVE describes integer overflow in the PFGc smart contract implementation affecting transfer, transferFrom, and mint. Provided metadata lacks CVSS, CWE, vendor, product, versions, deployed contract address, and patch information, so exposure must be confirmed through local asset and contract review.

Likely exposure

Exposure appears limited to organizations that hold, integrate with, audit, or depend on the affected PFGc Ethereum token contract or related forks. The source bundle does not identify a deployed address, version range, or vendor-owned product.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not report active exploitation. Integer overflow in token transfer or mint paths can create severe accounting effects if the vulnerable code is reachable, but exploitability cannot be confirmed from the bundle alone.

Researcher notes

The public metadata is sparse: no CVSS, CWE, affected vendor/product, version range, deployed address, patch, or exploit evidence is included. Analysis should center on confirming whether the referenced smart contract implementation exists in the environment and whether unsafe arithmetic is reachable.

Mitigation direction

  • Identify any business or technical dependency on PFGc or forks of its contract code.
  • Check project guidance for remediation, migration, or deprecation instructions.
  • Avoid new integrations until contract exposure and arithmetic safety are validated.
  • Review treasury, wallet, and exchange workflows for reliance on affected balances.
  • Use audited arithmetic protections in any replacement or forked token contract.

Validation and detection

  • Search inventories, wallets, and dApps for PFGc contract references.
  • Review source for unsafe arithmetic in transfer, transferFrom, and mint.
  • Compare deployed bytecode with the referenced vulnerable implementation where possible.
  • Check historical token supply and balance events for anomalies.
  • Document whether any affected contract is business-critical or externally exposed.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-13328 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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