FileRise: Login Method Restriction Bypass via Direct API Access
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.21.0, FileRise enforces disableFormLogin, disableBasicAuth, and disableOIDCLogin in the client interface but not consistently in the corresponding server-side authentication flows. A user with otherwise valid credentials for a disabled method can call its backend endpoint directly and authenticate despite the administrator's login-method policy. The flaw does not permit credential-free authentication. This issue is fixed in version 3.21.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-69191
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 20:06 UTC · Revision 1
Source evidence
FileRise: Login Method Restriction Bypass via Direct API Access
core-osv · Original sourcePublished 14 Oct 2026, 20:33 UTC
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.21.0, FileRise enforces disableFormLogin, disableBasicAuth, and disableOIDCLogin in the client interface but not consistently in the corresponding server-side authentication flows. A user with otherwise valid credentials for a disabled method can call its backend endpoint directly and authenticate despite the administrator's login-method policy. The flaw does not permit credential-free authentication. This issue is fixed in version 3.21.0.
osv:CVE-2026-69191
Complete source record
{
"id": "09e17f9c636fddcc4dfc1c9a9266ecc07295ecef7981cf4ff81ee41f6570c102",
"url": "https://osv.dev/vulnerability/CVE-2026-69191",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "FileRise: Login Method Restriction Bypass via Direct API Access",
"summary": "FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.21.0, FileRise enforces disableFormLogin, disableBasicAuth, and disableOIDCLogin in the client interface but not consistently in the corresponding server-side authentication flows. A user with otherwise valid credentials for a disabled method can call its backend endpoint directly and authenticate despite the administrator's login-method policy. The flaw does not permit credential-free authentication. This issue is fixed in version 3.21.0.",
"evidence": "osv:CVE-2026-69191",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-69191",
"aliases": [
"CVE-2026-69191",
"GHSA-p9qc-2r93-jccq"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/error311/filerise",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "82d99b0d9c52753dcaeafe8dfae46d7216d4d526"
},
{
"fixed": "613fdb28ca25e6dcc9bdfa590757b53935fad8da"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "3.21.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "613fdb28ca25e6dcc9bdfa590757b53935fad8da"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "82d99b0d9c52753dcaeafe8dfae46d7216d4d526"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v3.21.0"
}
]
}
}
],
"versions": [
"v3.20.0",
"v3.19.0",
"v3.18.0",
"v3.17.0",
"v3.16.0",
"v3.15.0",
"v3.14.0",
"v3.13.0",
"v3.12.0",
"v3.11.2",
"v3.11.1",
"v3.11.0",
"v3.10.0",
"v3.9.4",
"v3.9.3",
"v3.9.2",
"v3.9.1",
"v3.9.0",
"v3.8.0",
"v3.7.0",
"v3.6.1",
"v3.6.0",
"v3.5.2",
"v3.5.1",
"v3.5.0",
"v3.4.1",
"v3.4.0",
"v3.3.3",
"v3.3.2",
"v3.3.1",
"v3.3.0",
"v3.2.4",
"v3.2.3",
"v3.2.2",
"v3.2.1",
"v3.1.7",
"v3.1.6",
"v3.1.4",
"v3.1.3",
"v3.1.2",
"v3.1.1",
"v3.1.0",
"v3.0.2",
"v3.0.1",
"v3.0.0",
"v2.13.1",
"v2.13.0",
"v2.12.1",
"v2.12.0",
"v2.11.4",
"v2.11.3",
"v2.11.2",
"v2.11.1",
"v2.11.0",
"v2.10.5",
"v2.10.4",
"v2.10.1",
"v2.9.3",
"v2.9.2",
"v2.8.0",
"v2.7.1",
"v2.7.0",
"v2.6.2",
"v2.6.1",
"v2.5.2",
"v2.5.1",
"v2.5.0",
"v2.4.0",
"v2.3.7",
"v2.3.6",
"v2.3.5",
"v2.3.4",
"v2.3.2",
"v2.3.1",
"v2.3.0",
"v2.2.4",
"v2.2.3",
"v2.2.2",
"v2.2.1",
"v2.1.0",
"v2.0.4",
"v2.0.3",
"v2.0.2",
"v2.0.1",
"v1.9.14",
"v1.9.13",
"v1.9.12",
"v1.9.11",
"v1.9.10",
"v1.9.9",
"v1.9.8",
"v1.9.7",
"v1.9.6",
"v1.9.5",
"v1.9.4",
"v1.9.3",
"v1.9.2",
"v1.9.1",
"v1.9.0",
"v1.8.13",
"v1.8.12",
"v1.8.11",
"v1.8.10",
"v1.8.9",
"v1.8.8",
"v1.8.7",
"v1.8.6",
"v1.8.5",
"v1.8.4",
"v1.8.3",
"v1.8.2",
"v1.8.1",
"v1.8.0",
"v1.7.5",
"v1.7.4",
"v1.7.3",
"v1.7.2",
"v1.6.11",
"v1.6.10",
"v1.6.9",
"v1.6.8",
"v1.6.7",
"v1.6.6",
"v1.6.5",
"v1.6.3",
"v1.6.2",
"v1.6.1",
"v1.6.0",
"v1.5.3",
"v1.5.2",
"v1.5.1",
"v1.5.0",
"1.4.0",
"v1.3.15",
"v1.3.13",
"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.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.3",
"v1.1.2",
"v1.1.1",
"v1.1.0",
"v1.0.9",
"v1.0.8",
"v1.0.7",
"v1.0.6",
"v1.0.5",
"v1.0.4",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-69191.json"
}
}
],
"modified": "2026-10-28T02:30:23.073554078Z",
"provider": "osv",
"references": [
"https://github.com/error311/FileRise/releases/tag/v3.21.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/69xxx/CVE-2026-69191.json",
"https://github.com/error311/FileRise/security/advisories/GHSA-p9qc-2r93-jccq",
"https://nvd.nist.gov/vuln/detail/CVE-2026-69191",
"https://github.com/error311/FileRise/commit/613fdb28ca25e6dcc9bdfa590757b53935fad8da"
],
"provider_metadata": {
"cwe_ids": [
"CWE-287"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/69xxx/CVE-2026-69191.json"
}
},
"related_cves": [
{
"value": "CVE-2026-69191",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489638,
"published_at": "2026-10-14T20:33:33.368+00:00"
}