CVE-2025-15110VulnerabilityPublished 27 Dec 2025Updated 24 Feb 2026

CVE-2025-15110: jackq XCMS · Unrestricted Upload

Affects jackq XCMSSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Dec 2025
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-26.

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

AI-suggested

To mitigate CVE-2025-15110, organizations should first restrict access to the backend upload functionality to only trusted, authenticated users with necessary privileges. Implement strict access controls and monitor for unusual upload activity. Employ web application firewalls (WAFs) with rules to detect and block suspicious file uploads, such as those containing executable code or unusual file extensions. Conduct manual or automated code reviews to add server-side validation and sanitization of uploaded files, ensuring only allowed file types and sizes are accepted. If possible, isolate the upload directory from execution permissions to prevent uploaded files from being executed as code. Regularly audit user privileges to minimize the number of users with high-level access. Monitor logs for signs of exploitation attempts. Engage with the vendor for updates and apply patches promptly once released. Finally, maintain comprehensive backups and incident response plans to recover from potential compromises.

Description

A vulnerability has been found in jackq XCMS up to 3fab5342cc509945a7ce1b8ec39d19f701b89261. Affected is the function Upload of the file Admin/Home/Controller/ProductImageController.class.php of the component Backend. Such manipulation of the argument File leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2025-15110 is the potential for attackers with high-level authenticated access to upload arbitrary files to the server running jackq XCMS. This can lead to several risks including remote code execution, web shell deployment, data tampering, or denial of service. Since the vulnerability requires high privileges, the initial compromise vector is likely through credential theft or insider threat. However, once exploited, attackers can escalate their control over the system, potentially pivoting to other internal resources. Organizations relying on jackq XCMS for backend content management or e-commerce may face data breaches, service outages, or reputational damage. The lack of an official patch increases exposure time. The rolling release model and absence of versioned updates complicate timely remediation. Although no active exploits are reported, the public disclosure may attract attackers to develop weaponized exploits, increasing risk over time.

Summary

CVE-2025-15110 is a vulnerability identified in the jackq XCMS content management system, specifically in the Upload function of the ProductImageController.class.php file within the backend component. The vulnerability arises from insufficient validation or sanitization of the file upload parameter, allowing an attacker to perform unrestricted file uploads. This can be exploited remotely by an attacker who has high-level privileges (authenticated with high rights) to upload arbitrary files, including potentially malicious scripts or executables. The vulnerability is present in versions of jackq XCMS up to the commit hash 3fab5342cc509945a7ce1b8ec39d19f701b89261. The product uses a rolling release model, which complicates version tracking and patching. The vendor has been notified but has not yet issued a patch or update. The CVSS v4.0 base score is 5.1 (medium severity), reflecting the network attack vector, low complexity, no user interaction, but requiring high privileges. The impact on confidentiality, integrity, and availability is low to medium, as the attacker must already have elevated access. No known exploits have been observed in the wild, but public disclosure increases the likelihood of exploitation attempts. The vulnerability could lead to unauthorized code execution, data manipulation, or service disruption if exploited.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:30 UTC

Technical details

References

Community reviews

Related threats