dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-15109

HIGH · 7.3 CVSS v3.1 Published 2025-12-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unrestricted file upload vulnerability in the plupload upload.php handler of XCMS allows remote attackers to upload arbitrary file types without proper validation. This could enable execution of malicious code if uploaded files are stored in web-accessible directories.

MitigationImplement strict allowlist-based file validation (extension, MIME type, magic bytes), store uploads outside webroot or with non-executable permissions, and add runtime execution prevention via .htaccess or similar controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate XCMS installation
    Search web root for XCMS core files (index.php, config.php) or /xcms/ directory structure
    Affected if XCMS content management system is installed on the server
  2. Find plupload upload.php handler
    Search for plupload directory in common paths like /includes/plupload/, /assets/plupload/, or /vendor/plupload/ within the XCMS installation
    Affected if plupload upload.php file exists in the XCMS installation
  3. Verify upload endpoint is web-accessible
    Attempt to access the upload.php file via HTTP request (e.g., GET /path/to/plupload/upload.php) to confirm it responds without authentication barriers
    Affected if upload.php is directly reachable over the network without requiring authentication
  4. Check upload directory location
    Review XCMS configuration files or the upload.php code to determine the upload destination path; check if it resolves to a directory within the web document root
    Affected if Uploaded files are stored in a web-accessible directory (within public_html, htdocs, or similar)
  5. Confirm file type validation is absent
    Review the upload.php source code for file extension, MIME type, or magic byte validation logic; check for allowlist-based filtering
    Affected if No file type validation or allowlist-based filtering is implemented in the upload handler

System is affected if XCMS with an exposed plupload upload.php handler stores uploads in web-accessible directories without proper file type validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based file validation (extension, MIME type, magic bytes), store uploads outside webroot or with non-executable permissions, and add runtime execution prevention via .htaccess or similar controls.

Recommended fix Moderate confidence
  1. Remove the vulnerable plupload example file Public/javascripts/admin/plupload-2.1.2/examples/upload.php from production deployment - example files should never be deployed to production servers
  2. If the file is needed for functionality, move it outside the web document root or disable via web server configuration (e.g., .htaccess deny or nginx location block)
  3. Configure the web server to deny execution of uploaded files in any user-accessible upload directories
  4. Implement server-side file type validation (check MIME type and file extension whitelist) for any legitimate upload functionality
  5. Audit the codebase for any other plupload example files or unused development files that may expose similar vulnerabilities

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15109 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data