Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify PublicCMS with trade module
-
DeliverySend crafted requests to payment controllers
-
ExploitManipulate payment workflow state
-
ExecutionBypass payment verification
-
ImpactComplete fraudulent transaction
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Business logic errors
|
| Exploitation Conditions | Requires the PublicCMS trade module (publiccms-trade) to be installed and actively processing payments - base PublicCMS installations without e-commerce features are not vulnerable. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no special conditions - remote unauthenticated exploitation against default trade module configurations. Attack requires network access to the trade payment controller endpoints, but no authentication, specific user interaction, or non-default configuration settings. The business logic flaw is inherent to the payment workflow code, not dependent on optional features. Limiting factor: exploitation impact is constrained to payment manipulation (VI:L/VA:L) rather than full system compromise, and requires the target site to be running the vulnerable version 5.202506.d specifically. |
| Impact | Real-world risk is MODERATE with caveats. The CVSS 4.0 score of 5.5 reflects low impact to integrity and availability (VI:L/VA:L) with no confidentiality impact, but the attack vector is fully remote with no authentication required (AV:N/AC:L/PR:N/UI:N). The exploit maturity level E:P (Proof-of-concept) confirms publicly available attack code exists. However, exploitation requires the PublicCMS trade module to be deployed and actively processing payments - not all PublicCMS installations include e-commerce functionality. The vendor's non-response to disclosure raises concern about patch availability. SSVC decision factors: exploitation is public (exploit POC available), technical impact is partial (payment manipulation but not arbitrary code execution), and automatable (AV:N/AC:L suggests scriptable exploitation). Priority depends on whether your PublicCMS deployment uses the trade module - if trade features are enabled, this is HIGH priority due to payment fraud risk and public exploit; if trade module is unused or not installed, risk is NEGLIGIBLE. Missing signals: EPSS score not provided, not in CISA KEV (suggesting no widespread exploitation yet), exact attack mechanism not detailed in available references. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies a PublicCMS e-commerce site running version 5.202506.d. Using the publicly available exploit code from https://vulnplus-note.wetolink.com/share/ayeMf4xWK0ZZ, the attacker crafts HTTP requests directly to the vulnerable TradeOrderController.pay or TradePaymentController.pay endpoints, manipulating payment workflow parameters to bypass payment verification, alter transaction amounts, or mark unpaid orders as completed. This could enable purchasing products without payment, obtaining services fraudulently, or disrupting legitimate payment processing. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 17, 2026
Business logic flaws in PublicCMS 5.202506.d trade payment controller allow unauthenticated remote attackers to manipulate payment processing workflows, potentially enabling payment bypass or unauthorized transaction modifications. Publicly available exploit code exists demonstrating the attack. The vulnerability affects three payment-related functions (TradeOrderController.pay, TradePaymentController.pay, AccountGatewayComponent.pay) in the publiccms-trade module. Vendor was notified but did not respond, and no patch has been announced.
RemediationAI
No vendor-released patch identified at time of analysis - the vendor was contacted but did not respond to the disclosure. Organizations must implement compensating controls: (1) Disable the PublicCMS trade/payment module entirely if e-commerce functionality is not business-critical (eliminates attack surface but removes payment features). (2) Implement strict server-side payment state validation independent of client inputs - verify each payment workflow step server-side against expected state machine transitions, reject out-of-sequence requests (adds latency to payment processing, requires custom code). (3) Deploy web application firewall (WAF) rules to detect anomalous payment API access patterns, such as repeated calls to payment endpoints without corresponding order creation (may cause false positives during legitimate retries). (4) Enable comprehensive payment transaction logging and real-time monitoring for payment amount mismatches or status inconsistencies (detective control, not preventive). (5) Restrict network access to trade controller endpoints to known client IP ranges if architecture permits (breaks mobile/dynamic IP users). Monitor https://vuldb.com/vuln/364326 and Sanluan's official channels for patch announcements. Consider migrating to actively maintained CMS platforms if vendor remains non-responsive, as payment security flaws pose significant fraud risk.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PublicCMS is a Java-based content management system with e-commerce capabilities. This vulnerability affects the trade payment flow module (publiccms-trade), specifically three payment controller functions. The root cause is CWE-840 (Business Logic Errors), indicating flawed state management or validation in the payment processing workflow rather than a traditional injection or memory corruption vulnerability. Java-based payment flows typically involve multi-step processes (cart → order → payment gateway → confirmation), and business logic errors can allow attackers to manipulate transaction states, amounts, or payment statuses by sending requests out of sequence or with crafted parameters. The affected CPE (cpe:2.3:a:sanluan:publiccms:*:*:*:*:*:*:*:*) indicates the Sanluan vendor's PublicCMS product is impacted, with version 5.202506.d specifically identified.
Know when Publiccms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
Lifecycle Timeline
1DescriptionCVE.org
A security vulnerability has been detected in Sanluan PublicCMS 5.202506.d. Impacted is the function TradeOrderController.pay/TradePaymentController.pay/AccountGatewayComponent.pay of the file publiccms-trade/src/main/java/com/publiccms/controller/web/trade/TradeOrderController.java of the component Trade Payment Flow. The manipulation leads to business logic errors. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
An arbitrary file upload vulnerability in the component /cms/CmsWebFileAdminController.java of PublicCMS v4.0.202406 all
Deserialization of Untrusted Data in PublicCMS v.4.0.202302.e allows a remote attacker to execute arbitrary code via a c
An issue in the BAT file parameters of PublicCMS v4.0 allows attackers to execute arbitrary code. Rated critical severit
A remote code execution issue was discovered in PublicCMS V4.0.20180210. Rated critical severity (CVSS 9.8), this vulner
PublicCMS V5.202506.b is vulnerable to SSRF. in the chat interface of SimpleAiAdminController.
PublicCMS V5.202506.b is vulnerable to Cross Site Request Forgery (CSRF) in the CkEditorAdminController.
PublicCMS v4.0.202302.e was discovered to contain a remote commande execution (RCE) vulnerability via the cmdarray param
An arbitrary file upload vulnerability in the component /admin/cmsTemplate/doUpload of PublicCMS v4.0.202302.e allows at
An arbitrary file upload vulnerability in the component /admin/cmsTemplate/savePlaceMetaData of Public CMS v.4.0.202302.
An arbitrary file upload vulnerability in the component /admin/cmsTemplate/savePlace of PublicCMS v4.0.202302.e allows a
An arbitrary file upload vulnerability in the component /admin/cmsTemplate/save of PublicCMS v4.0.202302.e allows attack
An arbitrary file upload vulnerability in the component /admin/cmsWebFile/save of PublicCMS v4.0.202302.e allows attacke
EUVD-2026-30688
GHSA-9g77-xx5j-qgfr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB