CVE-2025-23918
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Enrico Sandoli Smallerik File Browser smallerik-file-browser allows Upload a Web Shell to a Web Server.This issue affects Smallerik File Browser: from n/a through <= 1.1.
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 confidenceThe Smallerik File Browser application suffers from an unrestricted file upload vulnerability that allows attackers to upload malicious web shell scripts to the web server. Due to insufficient validation of uploaded file types, an attacker can bypass restrictions and upload executable scripts (e.g., PHP, JSP, ASP) that can then be accessed via HTTP to achieve remote code execution.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Smallerik File Browser installationSearch for Smallerik File Browser in your installed applications, web server document roots, or running services. Check for directories named 'filebrowser', 'smallerik', or similar. Review your web server config for any file browser applications.Affected if Smallerik File Browser is present in the environment
-
Determine the installed versionCheck the application's about page, README, or configuration files for version information. Look in the application root directory for version markers.Affected if Version cannot be determined or is unknown (assume affected)
-
Verify if file upload feature is enabledAccess the file browser interface and attempt to locate an upload function. Check application configuration files for upload-related settings (e.g., enable_upload, allow_upload).Affected if File upload functionality is accessible to users
-
Test file type validationAttempt to upload a test file with executable extensions such as .php, .jsp, .asp, or .exe through the file browser upload interface. Observe whether the upload succeeds or is rejected.Affected if Executable file extensions are accepted and stored on the server
-
Check upload storage locationExamine application configuration or inspect where uploaded files are stored. Determine if the upload directory is within the web server's document root (webroot) or outside it.Affected if Uploaded files are stored within the webroot and accessible via HTTP
If Smallerik File Browser is installed with file upload enabled and accepts executable script extensions (PHP, JSP, ASP) that are stored in a web-accessible location, the environment is vulnerable to CVE-2025-23918.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict allowlist-based file validation checking both file extension AND content-type/magic bytes, store uploads outside webroot or disable script execution in the upload directory, and rename uploaded files to prevent direct execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2025-23918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23918 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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