dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-10172

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 security flaw has been discovered in Bdtask Multi-Store Inventory Management System 1.0. The affected element is the function Upload of the file application/modules/dashboard/controllers/Module.php of the component Component Module. The manipulation of the argument module results in unrestricted upload. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks.

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 · moderate confidence

The Bdtask Multi-Store Inventory Management System 1.0 contains an unrestricted file upload vulnerability in the Module.php dashboard controller's Upload function. Attackers can exploit the 'module' argument to upload arbitrary files (including executable scripts) to the server without proper validation, potentially achieving remote code execution.

MitigationImplement strict file type validation (allowlist approach), validate file content/magic bytes, rename uploaded files, store uploads outside the web root, and disable script execution in the upload directory.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Bdtask Multi-Store Inventory Management System installation
    Look for the application directory structure typical of Bdtask applications. Check for the presence of known Bdtask files such as index.php in the web root, or look for the 'bdtask' namespace or branding references in the source code.
    Affected if The application directory structure matches Bdtask Multi-Store Inventory Management System and the index.php entry point exists.
  2. Verify the product version is 1.0
    Check for a version file or configuration that states the application version. Common locations include a VERSION file in the root, a config file with a 'version' parameter, or the system information page within the application admin panel.
    Affected if The installed version is 1.0, as this is the affected version per the CVE summary.
  3. Locate the vulnerable Module.php file
    Inspect the file at application/modules/dashboard/controllers/Module.php for the presence of an Upload function. Verify that this file exists in the installation.
    Affected if The file application/modules/dashboard/controllers/Module.php exists and contains an Upload or upload method.
  4. Check if upload functionality is accessible
    Determine if the dashboard module and its controller are routed and accessible. Look for route definitions that map to the Module controller, typically accessible via a URL path like /dashboard/module/upload or similar.
    Affected if The upload endpoint is routed and publicly or semi-publicly accessible without additional authentication barriers.
  5. Verify upload directory is web-accessible
    Identify the upload directory used by the application. Check if this directory is within the web root (publicly accessible) and whether any .htaccess or configuration prevents script execution.
    Affected if The upload directory is inside the web root and allows execution of uploaded files (no script execution restrictions).

You are affected if you are running Bdtask Multi-Store Inventory Management System version 1.0, the vulnerable Module.php file with the Upload function exists, and the upload directory is web-accessible without script execution restrictions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file type validation (allowlist approach), validate file content/magic bytes, rename uploaded files, store uploads outside the web root, and disable script execution in the upload directory.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10172 — 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-2026-10172 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