How severe is CVE-2025-5136?

CVE-2025-5136 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2025-5136 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-5136?

CVE-2025-5136 affects Project Team Tmall Demo. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-5136?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-5136 have an EU (EUVD) identifier?

Yes. CVE-2025-5136 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16231.

When was CVE-2025-5136 published?

CVE-2025-5136 was published on 2025-05-25 and last updated on 2026-06-17.

CVE-2025-5136

CVE-2025-5136 is a low-severity vulnerability in Project Team Tmall Demo with a CVSS 3.x base score of 3.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-310.

Key facts

Severity: Low (CVSS 3.x base score 3.7)
CVSS v2: 2.6
CVSS v4: 6.3
EPSS exploit prediction: 0% (37th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-16231
Weakness: CWE-310
Affected product: Project Team Tmall Demo
Published: 2025-05-25
Last modified: 2026-06-17

Description

A vulnerability, which was classified as problematic, was found in Tmall Demo up to 20250505. This affects an unknown part of the file /tmall/order/pay/ of the component Payment Identifier Handler. The manipulation leads to insufficiently random values. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Frequently asked questions

What is CVE-2025-5136?: A vulnerability, which was classified as problematic, was found in Tmall Demo up to 20250505. This affects an unknown part of the file /tmall/order/pay/ of the component Payment Identifier Handler. The manipulation leads to insufficiently random values. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.
How severe is CVE-2025-5136?: CVE-2025-5136 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2025-5136 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-5136?: CVE-2025-5136 affects Project Team Tmall Demo. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-5136?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-5136 have an EU (EUVD) identifier?: Yes. CVE-2025-5136 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16231.
When was CVE-2025-5136 published?: CVE-2025-5136 was published on 2025-05-25 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:project_team:tmall_demo:*:*:*:*:*:*:*:*

More vulnerabilities in Project Team Tmall Demo

CVE-2024-40554 — High (CVSS 7.5): An access control issue in Tmall_demo v2024.07.03 allows attackers to obtain sensitive information.
CVE-2024-40560 — High (CVSS 7.3): Tmall_demo before v2024.07.03 was discovered to contain a SQL injection vulnerability.
CVE-2025-1843 — Medium (CVSS 6.3): A vulnerability, which was classified as critical, has been found in Mini-Tmall up to 20250211. This issue affects the…
CVE-2024-8568 — Medium (CVSS 6.3): A vulnerability, which was classified as critical, was found in Mini-Tmall up to 20240901. Affected is the function…
CVE-2024-40555 — Medium (CVSS 5.3): Tmall_demo v2024.07.03 was discovered to contain an arbitrary file upload vulnerability.
CVE-2024-40553 — Medium (CVSS 4.9): Tmall_demo v2024.07.03 was discovered to contain an arbitrary file upload via the component uploadUserHeadImage.

All CVEs affecting Project Team Tmall Demo →

Other CWE-310 (Cryptographic Issues) vulnerabilities

CVE-2014-7878 — Critical (CVSS 10.0): The Application Lifecycle Service (ALS) in HP Helion Cloud Development Platform 1.0, when a virtual machine is derived…
CVE-2013-3712 — Critical (CVSS 10.0): SUSE Studio Onsite 1.3.x before 1.3.6 and SUSE Studio Extension for System z 1.3 uses "static" secret tokens, which has…
CVE-2013-6952 — Critical (CVSS 10.0): The Belkin WeMo Home Automation firmware before 3949 has a hardcoded GPG key, which makes it easier for remote…
CVE-2013-6838 — Critical (CVSS 10.0): An unspecified Enghouse Interactive Professional Services "addon product" in Enghouse Interactive IVR Pro (VIP2000)…
CVE-2013-0137 — Critical (CVSS 10.0): The default configuration of the Digital Alert Systems DASDEC EAS device before 2.0-2 and the Monroe Electronics R189…
CVE-2011-5123 — Critical (CVSS 10.0): The Antivirus component in Comodo Internet Security before 5.3.175888.1227 does not check whether X.509 certificates in…

Browse all CWE-310 (Cryptographic Issues) vulnerabilities →