Quick answers
- Is CVE-2026-110113 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110113 being exploited in the wild.
- How severe is CVE-2026-110113?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- Sanluan PublicCMS through V6.202608.a.
- Is there a fix for CVE-2026-110113?
- 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-110113 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-110113?
- 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
The TradeAddressController.save endpoint accepts a user-supplied address ID and passes it directly to a generic update method without verifying ownership. The vulnerable code path loads the target row by primary key alone and overwrites fields (addressee, telephone, address) without checking that the address belongs to the authenticated user or site. Authentication (login) and CSRF tokens are enforced but do not provide object-level authorization; the delete handler in the same controller correctly implements ownership checks, showing the gap was unintended.
Affected products
- sanluan PublicCMS through V6.202608.a
Timeline
- 2026-10-13: disclosed