Skip to main content

PublicCMS CVE-2026-8738

| EUVDEUVD-2026-30688 MEDIUM
Business Logic Errors (CWE-840)
2026-05-17 VulDB GHSA-9g77-xx5j-qgfr
5.5
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify PublicCMS with trade module
  2. Delivery
    Send crafted requests to payment controllers
  3. Exploit
    Manipulate payment workflow state
  4. Execution
    Bypass payment verification
  5. Impact
    Complete 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

PublicCMS 5.202506.d

Affected Packages

euvd publiccms no fix

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

Vendor (VulDB) PRIMARY 5.5 MEDIUM
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

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
May 17, 2026 - 08:22 NVD
6.5 (MEDIUM) 5.5 (MEDIUM)

DescriptionCVE.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

EPSS Score
0.0%
Top 88% exploitable
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2025-25361 CRITICAL POC
9.8 Mar 06

An arbitrary file upload vulnerability in the component /cms/CmsWebFileAdminController.java of PublicCMS v4.0.202406 all

CVE-2023-46990 CRITICAL POC
9.8 Nov 20

Deserialization of Untrusted Data in PublicCMS v.4.0.202302.e allows a remote attacker to execute arbitrary code via a c

CVE-2021-40881 CRITICAL POC
9.8 Sep 15

An issue in the BAT file parameters of PublicCMS v4.0 allows attackers to execute arbitrary code. Rated critical severit

CVE-2018-12914 CRITICAL POC
9.8 Jun 27

A remote code execution issue was discovered in PublicCMS V4.0.20180210. Rated critical severity (CVSS 9.8), this vulner

CVE-2025-65836 CRITICAL POC
9.1 Dec 01

PublicCMS V5.202506.b is vulnerable to SSRF. in the chat interface of SimpleAiAdminController.

CVE-2025-65840 HIGH POC
8.8 Dec 01

PublicCMS V5.202506.b is vulnerable to Cross Site Request Forgery (CSRF) in the CkEditorAdminController.

CVE-2024-40552 HIGH POC
8.8 Jul 12

PublicCMS v4.0.202302.e was discovered to contain a remote commande execution (RCE) vulnerability via the cmdarray param

CVE-2024-40551 HIGH POC
8.8 Jul 12

An arbitrary file upload vulnerability in the component /admin/cmsTemplate/doUpload of PublicCMS v4.0.202302.e allows at

CVE-2024-40550 HIGH POC
8.8 Jul 12

An arbitrary file upload vulnerability in the component /admin/cmsTemplate/savePlaceMetaData of Public CMS v.4.0.202302.

CVE-2024-40549 HIGH POC
8.8 Jul 12

An arbitrary file upload vulnerability in the component /admin/cmsTemplate/savePlace of PublicCMS v4.0.202302.e allows a

CVE-2024-40548 HIGH POC
8.8 Jul 12

An arbitrary file upload vulnerability in the component /admin/cmsTemplate/save of PublicCMS v4.0.202302.e allows attack

CVE-2024-40546 HIGH POC
8.8 Jul 12

An arbitrary file upload vulnerability in the component /admin/cmsWebFile/save of PublicCMS v4.0.202302.e allows attacke

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy