Security readout for executives and security teams
This CVE describes a cross-site scripting flaw in the Amazon PAYFORT PHP SDK payment success page. If a site deployed the vulnerable SDK/payment flow, attacker-controlled input in the fort_id parameter could be reflected to users. For executives, the concern is payment-page trust and potential customer-session exposure, not confirmed large-scale exploitation. Exposure is most likely on PHP applications that integrated the legacy Amazon PAYFORT payfort-php-SDK and still serve its success.php payment-return page. Organizations not using this SDK or that removed the sample success page are less likely exposed. Prioritize inventory first, then remediate quickly if legacy PAYFORT PHP SDK payment pages remain public. The issue affects a sensitive customer trust boundary, but available evidence lacks severity scoring, exploit confirmation, and explicit patch details. Mitigation focus: Inventory applications using payfort-php-SDK or copied success.php code.; Check vendor or maintainer guidance for fixed SDK versions or replacement code.; Remove unused sample payment callback pages from production..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2018-19188 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/payfort/payfort-php-sdk/issues/12CVE reference · x_refsource_MISC
- https://www.seekurity.com/blog/general/payfort-multiple-security-issues-and-concerns-in-a-supposed-to-be-pci-dss-compliant-payment-processor-sdkCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.