dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-44460

HIGH · 7.4 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/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
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.12.0, /api/totp_setup.php is callable from a session that has only passed the password check (state pending_login_user). When the target account already has TOTP configured, the endpoint decrypts and returns the user's existing TOTP secret inside the QR PNG instead of refusing or generating a new secret. An attacker who already possesses the victim's password can therefore retrieve the live TOTP secret, derive a valid one-time code, submit it to /api/totp_verify.php, and obtain a fully authenticated session without ever possessing the victim's authenticator device. This vulnerability is fixed in 3.12.0.

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

The /api/totp_setup.php endpoint in FileRise prior to 3.12.0 can be called during the pending_login_user session state (after password check but before full authentication). When the target account already has TOTP configured, the endpoint decrypts and returns the user's existing TOTP secret in the QR PNG rather than refusing the request or generating a new secret. An attacker with the victim's password can retrieve this secret, generate valid one-time codes, and complete authentication without the victim's authenticator device.

MitigationUpgrade to FileRise version 3.12.0 or later, which properly validates authentication state before returning TOTP secrets.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Identify FileRise installation and version
    Check the application version by examining version files, composer.json, or the main application header/footer for a version number. Common paths include /composer.json, /version.php, or the admin dashboard.
    Affected if FileRise version is present and is below 3.12.0 (e.g., 3.11.x, 3.10.x, etc.)
  2. Confirm TOTP authentication is enabled
    Check if TOTP/2FA is configured in the application's settings, user profile pages, or authentication configuration files. Look for totp_enabled, two_factor_auth, or similar configuration flags.
    Affected if TOTP/two-factor authentication has been enabled for any user account in the system
  3. Verify the vulnerable endpoint exists
    Check if /api/totp_setup.php file exists in the web root or application API directory.
    Affected if The file /api/totp_setup.php exists and is accessible via the web server
  4. Check session state handling for pending_login_user
    Review application code or session configuration to confirm that pending_login_user is a valid session state between password verification and full authentication.
    Affected if The application uses a multi-step login where pending_login_user is a valid intermediate session state after password check but before complete authentication
  5. Determine if users have existing TOTP secrets
    Query the database or user configuration to check if any user accounts already have TOTP secrets configured (non-null/non-empty totp_secret field).
    Affected if At least one user account has an existing TOTP secret stored in the system

The environment is affected if FileRise version is below 3.12.0 AND TOTP is enabled for at least one user AND the /api/totp_setup.php endpoint exists, allowing a user in pending_login_user state to retrieve existing TOTP secrets.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to FileRise version 3.12.0 or later, which properly validates authentication state before returning TOTP secrets.

Recommended fix High confidence

3.12.0

  1. Check the currently installed FileRise version by examining the application or version file
  2. Download FileRise version 3.12.0 or later from the official repository
  3. Backup the existing FileRise installation and database
  4. Replace the existing installation files with the new version
  5. Verify the /api/totp_setup.php endpoint now properly handles the pending_login_user state and does not expose existing TOTP secrets

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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