Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-6497

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was determined in prasathmani TinyFileManager up to 2.6. Affected by this vulnerability is an unknown functionality of the file /filemanager.php?p= ajax=true&type=upload of the component File Upload Handler. This manipulation of the argument uploadurl causes server-side request forgery. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

TinyFileManager versions up to 2.6 contain a Server-Side Request Forgery (SSRF) vulnerability in the file upload handler at /filemanager.php. The uploadurl parameter is not validated, allowing remote attackers to force the server to make arbitrary HTTP requests to internal or external resources by manipulating this parameter.

MitigationImplement strict allowlist validation for the uploadurl parameter to restrict URLs to trusted domains only, or disable the upload URL functionality entirely if not required. Consider network segmentation to limit outbound access from the web server.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Locate TinyFileManager installation and determine version
    Search for filemanager.php on the web server and check for a version constant or version file (often in a config.php, version.php, or the main filemanager.php header comments)
    Affected if The installed version is 2.6 or any earlier version
  2. Verify the vulnerable endpoint exists
    Confirm that /filemanager.php exists and is accessible on the web server
    Affected if The file /filemanager.php is present and publicly accessible
  3. Identify if upload URL functionality is enabled
    Examine the filemanager.php source code for the uploadurl parameter handling; look for sections that process the 'uploadurl' or 'url' parameter in file upload logic
    Affected if The uploadurl parameter is processed without validation in the upload handler
  4. Check for absence of URL validation on uploadurl parameter
    Search the filemanager.php code for validation logic on the uploadurl parameter (look for allowlist checks, URL validation functions, or whitelist domains)
    Affected if No strict allowlist or validation is found for the uploadurl parameter before it is used in HTTP requests
  5. Test for SSRF accessibility (optional indirect check)
    If authorized in your own environment, observe network connections from the web server when the uploadurl parameter is supplied with a test URL (e.g., a controlled internal endpoint)
    Affected if The server successfully makes outbound HTTP requests to arbitrary URLs supplied via the uploadurl parameter

Your environment is affected if TinyFileManager version 2.6 or earlier is installed, the filemanager.php endpoint exists, and the upload URL feature with the uploadurl parameter is enabled without proper validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist validation for the uploadurl parameter to restrict URLs to trusted domains only, or disable the upload URL functionality entirely if not required. Consider network segmentation to limit outbound access from the web server.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6497 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