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

CVE-2025-15109: jackq XCMS · Unrestricted Upload

Affects jackq XCMSSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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-15109, organizations should first identify all instances of jackq XCMS in their environment, focusing on those exposing the vulnerable upload.php endpoint. 2) Implement strict input validation and file type restrictions on uploaded files, allowing only necessary file types and rejecting all others. 3) Employ web application firewalls (WAFs) with rules to detect and block malicious upload attempts targeting plupload or upload.php. 4) Monitor logs for suspicious upload activity or unexpected file creations in web directories. 5) If feasible, temporarily disable or remove the vulnerable upload functionality until a vendor patch is released. 6) Follow the jackq project closely for updates or patches and apply them promptly once available. 7) Conduct regular security assessments and penetration tests to detect any exploitation attempts. These targeted actions go beyond generic advice by focusing on access control, input validation, and proactive monitoring specific to the vulnerable component.

Description

A flaw has been found in jackq XCMS up to 3fab5342cc509945a7ce1b8ec39d19f701b89261. This impacts an unknown function of the file Public/javascripts/admin/plupload-2.1.2/examples/upload.php. This manipulation causes unrestricted upload. It is possible to initiate the attack remotely. The exploit has been published and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The unrestricted upload vulnerability in jackq XCMS can have significant impacts on organizations using this CMS. Attackers can remotely upload malicious files such as web shells or scripts, enabling them to execute arbitrary code, escalate privileges, or move laterally within the network. This compromises confidentiality by exposing sensitive data, integrity by allowing unauthorized modifications, and availability by potentially disrupting services. Since no authentication or user interaction is required, exploitation is straightforward, increasing risk. Organizations relying on jackq XCMS for web content management may face website defacement, data breaches, or full system compromise. The rolling release model and lack of vendor response increase exposure duration. Additionally, the presence of a public exploit raises the likelihood of opportunistic attacks. Overall, this vulnerability threatens the security posture of affected organizations, especially those with internet-facing XCMS deployments.

Summary

CVE-2025-15109 identifies an unrestricted file upload vulnerability in jackq XCMS, specifically within the file Public/javascripts/admin/plupload-2.1.2/examples/upload.php. The vulnerability arises because the upload.php script does not properly restrict or validate uploaded files, allowing an attacker to remotely upload arbitrary files without requiring authentication or user interaction. This can lead to remote code execution or unauthorized system access if malicious files such as web shells are uploaded and executed. The vulnerability affects the codebase up to commit 3fab5342cc509945a7ce1b8ec39d19f701b89261. jackq XCMS employs a rolling release model, meaning continuous delivery without fixed version numbers, which complicates identifying affected versions and applying patches. The vendor has been notified but has not yet issued a fix or response. The CVSS v4.0 base score is 6.9 (medium), reflecting network attack vector, no privileges or user interaction required, and partial impact on confidentiality, integrity, and availability. While no active exploitation has been confirmed, a public exploit is available, increasing the urgency for mitigation. The vulnerability leverages a common web application weakness—unrestricted file upload—often exploited to gain persistent unauthorized access or execute arbitrary code on the server.

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