Quick answers
- Is CVE-2026-8737 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8737 being exploited in the wild.
- How severe is CVE-2026-8737?
- Medium severity, with a CVSS score of 5.3, published 17 May 2026.
- Which products and versions are affected?
- Sanluan PublicCMS 5.202506.d.
- Is there a fix for CVE-2026-8737?
- 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-8737 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-8737?
- 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 missing authentication vulnerability exists in the TradeAddressListDirective and TradeAddressDirective components of Sanluan PublicCMS. The affected directives inherit from AbstractTemplateDirective but fail to override the needAppToken() or needUserToken() methods, leaving the /api/directive/trade/addressList and /api/directive/trade/address endpoints accessible to unauthenticated users. By manipulating the 'userId' or 'id' parameters in a GET request, a remote attacker can bypass authorization checks to retrieve TradeAddress entity data. This data includes sensitive fields such as the addressee name, physical address, and telephone number. A public exploit is available, and the vendor has reportedly not responded to disclosure attempts.
Affected products
- Sanluan PublicCMS 5.202506.d
Timeline
- 2026-05-17: advisory: Vulnerability disclosed via VulDB and NVD