dbcve.org
FilrApplication · Opentext

CVE-2026-3266

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-03
Fix available
A fix is available. Upgrade to 25.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in OpenText™ Filr allows Authentication Bypass. The vulnerability could allow unauthenticated users to get XSRF token and do RPC with carefully crafted programs. This issue affects Filr: through 25.1.2.

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

Missing authorization in OpenText Filr allows unauthenticated users to obtain XSRF tokens and execute RPC calls, effectively bypassing authentication controls. The vulnerability affects all versions through 25.1.2 and can be exploited with carefully crafted requests.

MitigationUpgrade to patched version of Filr immediately. If immediate patching is not feasible, restrict network access to the Filr interface using firewall rules or network segmentation to limit exposure.

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
FilrApplication
Affected:< 25.1.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Filr installation version
    Access the Filr administration interface or check the product version through the help/about section. Alternatively, inspect the product installation directory for version metadata files or check the RPM/DEB package version if installed via package manager.
    Affected if Installed version is earlier than 25.1.3 (e.g., 25.1.2, 25.1.1, 25.1.0, or any version through 25.1.2) and falls within the affected range.
  2. Verify RPC endpoint accessibility
    Send an unauthenticated HTTP request to common Filr RPC endpoints (typically found under /rpc/ or /services/ paths). Use a tool like curl to send a request without providing authentication credentials and observe the response.
    Affected if The server returns a valid response (rather than redirecting to a login page or returning 401/403) indicating the RPC interface accepts unauthenticated requests.
  3. Confirm XSRF token exposure
    Capture HTTP responses from Filr endpoints while unauthenticated. Inspect response headers and body for the presence of XSRF tokens (often named XSRF-TOKEN, Csrf-Token, or similar) being issued to unauthenticated sessions.
    Affected if XSRF tokens are issued to unauthenticated users, confirming the token leakage described in the CVE.

Your environment is affected if Filr is installed at any version prior to 25.1.3 AND the RPC interface is accessible to unauthenticated users, allowing them to obtain XSRF tokens and execute privileged calls.

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 25.1.3 or later
Fixed in 25.1.3
Interim mitigation

Upgrade to patched version of Filr immediately. If immediate patching is not feasible, restrict network access to the Filr interface using firewall rules or network segmentation to limit exposure.

Recommended fix High confidence

Filr 25.1.3

  1. Backup the current Filr installation and database before proceeding with the upgrade
  2. Stop the Filr services to ensure a clean upgrade process
  3. Download Filr version 25.1.3 or later from the official OpenText/Micro Focus download portal
  4. Install the upgrade following the standard Filr upgrade documentation
  5. After installation, verify that the Filr services start successfully
  6. Confirm the upgrade was successful by checking the Filr version in the administration interface
  7. Test that authentication is working properly and the authorization controls are enforced

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

Fix this in Filr Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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