# CVE-2026-8738: Sanluan PublicCMS business logic error in Trade Payment Flow

Source: https://junglewise.ai/threats/cve-2026-8738-sanluan-publiccms-business-logic-error-in-trade-payment-flow  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-17. Updated: 2026-05-17  
License: CC BY 4.0 with a link back

CVE-2026-8738 · Severity: medium · CVSS 6.5 · Published 2026-05-17

A business logic vulnerability in Sanluan PublicCMS allows unauthorized individuals to manipulate the payment process. An attacker can remotely force a victim's pending order to be paid using the victim's own internal account balance without their consent. This can lead to unauthorized financial transactions and the depletion of user account funds.

Technologies: [Sanluan PublicCMS](https://junglewise.ai/threats/technologies/publiccms). Vendors: [Sanluan](https://junglewise.ai/threats/vendors/sanluan).

## Quick answers

**Is CVE-2026-8738 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-8738 being exploited in the wild.

**How severe is CVE-2026-8738?** Medium severity, with a CVSS score of 6.5, published 17 May 2026.

**Which products and versions are affected?** Sanluan PublicCMS 5.202506.d.

**Is there a fix for CVE-2026-8738?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-8738 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-8738?** Check whether you run Sanluan PublicCMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A business logic error exists in the Trade Payment Flow component of PublicCMS, specifically within the TradeOrderController.pay, TradePaymentController.pay, and AccountGatewayComponent.pay functions. The application fails to perform authentication or ownership validation when initiating or executing a payment. An unauthenticated attacker can supply a victim's order ID to the payment endpoint; the system then creates a payment record and deducts funds from the internal balance associated with the order owner (payment.userId) without verifying the identity of the requester. This allows for remote, pre-authentication exploitation of financial transactions. As of the advisory date, the vendor has not responded to the disclosure.

## Affected products

- Sanluan PublicCMS 5.202506.d

## Timeline

- 2026-05-17: advisory: Vulnerability disclosed via VulDB and NVD
- 2026-05-17: disclosed: Public disclosure of the exploit details

## References

- [https://vuldb.com/submit/809905](https://vuldb.com/submit/809905)
- [https://vuldb.com/vuln/364326](https://vuldb.com/vuln/364326)
- [https://vuldb.com/vuln/364326/cti](https://vuldb.com/vuln/364326/cti)
- [https://vulnplus-note.wetolink.com/share/ayeMf4xWK0ZZ](https://vulnplus-note.wetolink.com/share/ayeMf4xWK0ZZ)

## Related threats

- [Sanluan PublicCMS authorization bypass in trade payment](https://junglewise.ai/threats/cve-2026-121583-a-vulnerability-was-identified-in-sanluan-publiccms-5-this)
- [Sanluan PublicCMS authorization bypass in TradeRefundService](https://junglewise.ai/threats/cve-2026-120319-a-vulnerability-was-found-in-sanluan-publiccms-4-x-5-x-6-x-this)
- [PublicCMS insecure direct object reference in TradeAddressController](https://junglewise.ai/threats/cve-2026-110113-publiccms-through-v6-202608-a-contains-an-insecure-direct-object)
- [Sanluan PublicCMS SSTI and auth bypass in templateResult API](https://junglewise.ai/threats/cve-2026-8740-sanluan-publiccms-ssti-and-auth-bypass-in-templateresult-api)
- [Sanluan PublicCMS hard-coded cryptographic key in private file access](https://junglewise.ai/threats/cve-2026-8739-sanluan-publiccms-hard-coded-cryptographic-key-in-private-file)