CVE-2024-40555VulnerabilityPublished 15 Jul 2024Updated 22 Nov 2024

CVE-2024-40555: Tmall_demo · n/a

Affects Tmall_demoSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubproject_team/Tmall_demo`pkg:github/project_team/Tmall_demo`Other threats	Affected =2024.07.03	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor official vendor channels for patches or updates addressing CVE-2024-40555 and apply them promptly once available. 2. Implement strict server-side validation of uploaded files, including checking file extensions, MIME types, and file content signatures to prevent unauthorized file types. 3. Enforce file upload size limits and restrict upload directories to non-executable locations to reduce the risk of malicious file execution. 4. Use allowlists for permitted file types rather than blocklists to minimize bypass opportunities. 5. Employ web application firewalls (WAFs) with rules designed to detect and block suspicious file upload attempts. 6. Regularly audit and monitor file upload directories for unexpected or suspicious files and remove them immediately. 7. Harden server configurations to prevent execution of uploaded files, such as disabling script execution in upload folders. 8. Conduct security testing and code reviews focusing on file upload functionality to identify and remediate weaknesses proactively. 9. Educate development teams on secure coding practices related to file handling and input validation. 10. Consider implementing multi-factor authentication and network segmentation to limit the impact of potential compromise.

Description

Tmall_demo v2024.07.03 was discovered to contain an arbitrary file upload vulnerability.

Impact

The primary impact of CVE-2024-40555 is on the integrity of affected systems, as attackers can upload arbitrary files that may alter or add malicious content. This can lead to unauthorized code execution, persistent backdoors, or defacement if the uploaded files are executed or served by the application. Although confidentiality and availability are not directly impacted according to the CVSS vector, the integrity compromise can indirectly lead to broader security breaches, including data theft or service disruption. The vulnerability is exploitable remotely without authentication or user interaction, increasing the risk of automated or mass exploitation attempts once public details become widespread. Organizations relying on Tmall_demo for e-commerce or other critical services could face reputational damage, financial loss, and operational disruption if exploited. The absence of known exploits in the wild currently limits immediate risk, but the medium severity score and ease of exploitation warrant proactive mitigation. Failure to address this vulnerability could expose organizations to targeted attacks or opportunistic exploitation by cybercriminals.

References

gitee.com/project_team/Tmall_demo/issues/IAAO1T (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 06:49 UTC

Technical details

References

Community reviews

Related threats