setup-eghl

Warn

Audited by Snyk on Nov 16, 2026

Risk Level: MEDIUM
Full Analysis

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (low risk: 0.10). The required workflow reads only first-party eGHL/ADAPTIS docs and SDK/plugin sources, but when debugging it may consume callback and return payloads that an outsider can forge by POSTing to the merchant's MerchantCallBackURL, so the agent could ingest attacker-supplied fields only after actively pulling those logs.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

  • Direct money access detected (medium risk: 0.30). The skill is mainly integration guidance for building and debugging eGHL/ADAPTIS payment flows, which is excluded as development. However, Core Workflow step 9 (SKILL.md:32) documents performing refunds (CC only, partial allowed, SKILL.md:50), reversals (RSALE) and captures through Payment.aspx with a signed server-side POST (SKILL.md:38). Those are direct money-moving operations (refund and reversal), so the skill is not purely illustrative. Their operational nature is not diminished by the code being explained.

Control: the route requires the Merchant Service ID and Merchant Password (SKILL.md:25), and the request is signed with the password-based HashValue over ServiceID, PaymentID, Amount and CurrencyCode (SKILL.md:42). The password must stay server-side (SKILL.md:54). These are validated service API credentials that gate the refund, reversal and capture route, so this is treated as an established service-enforced authentication mechanism. The file does not explicitly state that the gateway validates the request hash, so this rests on the credential requirement rather than a detailed description of enforcement. That is the main ambiguity, and it is why this is not rated high.

SALE and Query are the same endpoint family, but the operational finding rests on refund, reversal and capture. The highest applicable tier is medium.

Issues (2)

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

W009
MEDIUM

Direct money access capability detected (payment gateways, crypto, banking).

Audit Metadata
Risk Level
MEDIUM
Analyzed
Nov 16, 2026, 05:13 AM
Issues
2