dbcve.org
Minigal NanoApplication · Rybber

CVE-2026-25869

HIGH · 7.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to after 0.3.5 or later.
See remediation →
84/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
MiniGal Nano versions 0.3.5 and prior contain a path traversal vulnerability in index.php via the dir parameter. The application appends user-controlled input to the photos directory and attempts to prevent traversal by removing dot-dot sequences, but this protection can be bypassed using crafted directory patterns. An attacker can exploit this behavior to cause the application to enumerate and display image files from unintended filesystem locations that are readable by the web server, resulting in unintended information disclosure.

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

MiniGal Nano 0.3.5 and prior contains a path traversal vulnerability in index.php via the 'dir' parameter. The application appends user-controlled input to the photos directory and attempts to block traversal by removing dot-dot (..) sequences, but this protection can be bypassed using crafted directory patterns, allowing attackers to read image files from arbitrary filesystem locations accessible to the web server.

MitigationImplement strict input validation on the 'dir' parameter using realpath() to canonicalize paths and verify the resolved path stays within the intended photos directory, or employ a whitelist approach for allowed directories.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Minigal NanoApplication
Affected:<= 0.3.5

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
High
Integrity
None
Availability
None

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

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 MiniGal Nano installation
    Search the web server document root for the presence of 'index.php' and look for Minigal Nano files (templates, config, etc.)
    Affected if MiniGal Nano files are present on the server
  2. Identify installed version
    Open index.php and look for a version variable or string (often near the top in comments or a defined constant). Compare against 0.3.5.
    Affected if The version string shows 0.3.5 or any version prior to it
  3. Verify index.php handles the dir parameter
    Inspect index.php source code and locate where the 'dir' parameter is processed (search for $_GET['dir'] or similar). Confirm it performs string concatenation to build a path.
    Affected if The code shows $_GET['dir'] being used to construct file paths without proper validation
  4. Confirm blacklist-based sanitization exists
    Search the index.php code for string manipulation that strips '..' sequences (look for str_replace, preg_replace targeting dot-dot patterns)
    Affected if The code uses str_replace or similar to remove '..' as a blacklist filter instead of realpath() validation
  5. Check application accessibility
    Determine if the web server serves the MiniGal Nano directory publicly and the index.php is reachable via HTTP
    Affected if The vulnerable index.php is accessible over the network and accepts user input

The environment is affected if MiniGal Nano version 0.3.5 or prior is installed and accessible, with index.php processing the 'dir' parameter using blacklist-based traversal sanitization.

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
Upgrade available Upgrade to a release after 0.3.5
Interim mitigation

Implement strict input validation on the 'dir' parameter using realpath() to canonicalize paths and verify the resolved path stays within the intended photos directory, or employ a whitelist approach for allowed directories.

Recommended fix Moderate confidence

latest stable release (check SourceForge for version newer than 0.3.5)

  1. 1. Backup the current Minigal Nano installation and its configuration files
  2. 2. Download the latest version of Minigal Nano from the official SourceForge repository
  3. 3. Replace all files in the existing installation with the files from the new version, preserving local configuration if applicable
  4. 4. Verify the new version by checking the version number displayed in the gallery footer
  5. 5. Test that the dir parameter now properly restricts access to the designated photos directory only
  6. 6. Confirm that path traversal attempts using dot-dot sequences are blocked or handled safely in the updated version

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

Fix this in Minigal Nano Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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