File Browser has Insecure File Permissions
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. The file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers using File Browser prior to version 2.33.7 where the umask configuration has not been hardened before, this makes all the stated files readable by any operating system account. Version 2.33.7 fixes the issue.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-52900
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 17:01 UTC · Revision 1
Source evidence
File Browser has Insecure File Permissions
core-osv · Original sourcePublished 26 Jun 2025, 14:35 UTC
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. The file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers using File Browser prior to version 2.33.7 where the umask configuration has not been hardened before, this makes all the stated files readable by any operating system account. Version 2.33.7 fixes the issue.
osv:CVE-2025-52900
Complete source record
{
"id": "f5b2a8702a2ad59e89b7a8bc7423aaa1f6990465e28ed861ec4c2cbf908667c3",
"url": "https://osv.dev/vulnerability/CVE-2025-52900",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "File Browser has Insecure File Permissions",
"summary": "File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. The file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers using File Browser prior to version 2.33.7 where the umask configuration has not been hardened before, this makes all the stated files readable by any operating system account. Version 2.33.7 fixes the issue.",
"evidence": "osv:CVE-2025-52900",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2025-52900",
"aliases": [
"CVE-2025-52900",
"GHSA-jj2r-455p-5gvf",
"GO-2025-3785"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/filebrowser/filebrowser",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "d6d84e2b48bd4c4268e1774e44a1186e04a8c054"
},
{
"fixed": "ca86f916216620365c0f81629c0934ce02574d76"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:filebrowser:filebrowser:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "2.33.7"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "ca86f916216620365c0f81629c0934ce02574d76"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v2.33.6",
"v2.33.5",
"v2.33.4",
"v2.33.3",
"v2.33.2",
"v2.33.1",
"v2.33.0",
"v2.32.3",
"v2.32.2",
"v2.32.1",
"v2.32.0",
"v2.31.2",
"v2.31.1",
"v2.31.0",
"v2.30.0",
"v2.29.0",
"v2.28.0",
"v2.27.0",
"v2.26.0",
"v2.25.0",
"v2.24.2",
"v2.24.1",
"v2.24.0",
"v2.23.0",
"v2.22.4",
"v2.22.3",
"v2.22.2",
"v2.22.1",
"v2.22.0",
"v2.21.1",
"v2.21.0",
"v2.20.1",
"v2.20.0",
"v2.19.0",
"v2.18.0",
"v2.17.2",
"v2.17.1",
"v2.17.0",
"v2.16.1",
"v2.16.0",
"v2.15.0",
"v2.14.1",
"v2.14.0",
"v2.13.0",
"v2.12.1",
"v2.12.0",
"v2.11.0",
"v2.10.0",
"v2.9.0",
"v2.8.0",
"v2.7.0",
"v2.6.2",
"v2.6.1",
"v2.6.0",
"v2.5.0",
"v2.4.0",
"v2.3.0",
"v2.2.0",
"v2.1.2",
"v2.1.1",
"v2.1.0",
"v2.0.16",
"v2.0.15",
"v2.0.14",
"v2.0.13",
"v2.0.12",
"v2.0.11",
"v2.0.10",
"v2.0.9",
"v2.0.8",
"v2.0.7",
"v2.0.6",
"v2.0.5",
"v2.0.4",
"v2.0.3",
"v2.0.2",
"v2.0.1",
"v2.0.0",
"v2.0.0-rc.2",
"v2.0.0-rc.1",
"v1.11.0",
"v1.10.0",
"v1.9.0",
"v1.8.0",
"v1.7.1",
"v1.7.0",
"v1.6.0",
"v1.5.5",
"v1.5.4",
"v1.5.3",
"v1.5.2",
"v1.5.1",
"v1.5.0",
"v1.4.6",
"v1.4.5",
"v1.4.4",
"v1.4.3",
"v1.4.0",
"v1.3.12",
"v1.3.11",
"v1.3.10",
"v1.3.9",
"v1.3.8",
"v1.3.7",
"v1.3.6",
"v1.3.5",
"v1.3.4",
"v1.3.3",
"v1.3.2",
"v1.3.1",
"v1.3.0",
"v1.2.9",
"v1.2.8",
"v1.2.7",
"v1.2.6",
"v1.2.5",
"v1.2.4",
"v1.2.3",
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.1",
"v1.1.0",
"v1.0.2",
"v1.0.1",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-52900.json"
}
}
],
"modified": "2026-10-28T02:30:37.978914444Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/52xxx/CVE-2025-52900.json",
"https://github.com/filebrowser/filebrowser/security/advisories/GHSA-jj2r-455p-5gvf",
"https://nvd.nist.gov/vuln/detail/CVE-2025-52900",
"https://github.com/filebrowser/filebrowser/commit/ca86f916216620365c0f81629c0934ce02574d76"
],
"provider_metadata": {
"cwe_ids": [
"CWE-276"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/52xxx/CVE-2025-52900.json"
}
},
"related_cves": [
{
"value": "CVE-2025-52900",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 505096,
"published_at": "2025-06-26T14:35:50.452+00:00"
}