DBRisinajumi d2files SQL Injection vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2015-10018: 0.71% estimated exploitation activity in the next 30 days; percentile 53.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability has been found in DBRisinajumi d2files and classified as critical. Affected by this vulnerability is the function actionUpload/actionDownloadFile of the file controllers/D2filesController.php. The manipulation leads to sql injection. Upgrading to version 1.0.0 can address this issue. The name of the patch is b5767f2ec9d0f3cbfda7f13c84740e2179c90574. It is recommended to upgrade the affected component. The identifier VDB-217561 was assigned to this vulnerability.

Published by the source

6 Jan 2023, 15:30 UTC

Last modified by the source

20 Oct 2023, 18:41 UTC

Source last checked

26 Oct 2026, 14:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-68hv-8926-j34c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2015-10018

Advisory: DBRisinajumi d2files SQL Injection vulnerability
IDs: CVE-2015-10018, GHSA-68hv-8926-j34c
Record: https://patchnext.com/advisories/cve-2015-10018 (revision 1, source checked 26 Oct 2026, 14:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dbrisinajumi/d2files 1.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist dbrisinajumi/d2files: affected < 1.0.0; fixed in 1.0.0

## Suggested inspection (read-only)
- Packagist dbrisinajumi/d2files: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dbrisinajumi/d2files.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-68hv-8926-j34c (GitHub-reviewed advisory GHSA-68hv-8926-j34c lists affected ranges: Packagist dbrisinajumi/d2files >=0 <1.0.0)

Commands are suggestions: review each one before running it.