Is CVE-2026-121583 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-121583 being exploited in the wild.

How severe is CVE-2026-121583?

Medium severity, with a CVSS score of 6.3, published 4 November 2026.

Is there a fix for CVE-2026-121583?

Yes: fixed in 202608 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-121583 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-121583?

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.

CVE-2026-121583: Sanluan PublicCMS authorization bypass in trade payment

CVE-2026-121583 · Severity: medium · CVSS 6.3 · Published 2026-11-04

PublicCMS is a content management system that includes e-commerce trade payment functionality. An authorization bypass vulnerability in the payment service allows remote attackers to manipulate user IDs and perform actions they are not authorized for, potentially accessing or modifying payment transactions belonging to other users. The vulnerability was removed in version 202608 and later.

Technologies: Sanluan PublicCMS. Vendors: Sanluan.

Quick answers

Is CVE-2026-121583 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-121583 being exploited in the wild.
How severe is CVE-2026-121583?: Medium severity, with a CVSS score of 6.3, published 4 November 2026.
Which products and versions are affected?: Sanluan PublicCMS 5.
Is there a fix for CVE-2026-121583?: Yes: fixed in 202608 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-121583 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-121583?: 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.

How to fix

Fixed in: 202608 and later

Technical details

The TradePaymentService.pendingRefund method in PublicCMS 5 fails to properly validate or authorize the userId parameter, allowing an authenticated or remote attacker to bypass authorization checks by manipulating this argument. This enables unauthorized access to refund operations and potentially other payment-related transactions. The issue was remediated by removing the vulnerable web trade payment controller starting with the 202608 series.

Affected products

Sanluan PublicCMS 5

Timeline

2026-11-04: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.