dbcve.org
RichfilemanagerApplication · Psolom

CVE-2025-63994

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
An arbitrary file upload vulnerability in the /php/UploadHandler.php component of RichFilemanager v2.7.6 allows attackers to execute arbitrary code via uploading a crafted file.

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

Arbitrary file upload vulnerability in the /php/UploadHandler.php component of RichFilemanager v2.7.6 allows unauthenticated attackers to upload malicious files (e.g., web shells) to the server and achieve remote code execution.

MitigationImplement strict server-side file type validation using magic bytes/file signatures, disable script execution in upload directories via .htaccess or web server config, apply content-disposition headers to force download, and upgrade to patched version if available.

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
RichfilemanagerApplication
Affected:= 2.7.6

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. Locate RichFilemanager installation
    Search for RichFilemanager directories on the web server, typically found in web root paths such as /filemanager, /richfilemanager, /rfm, or as part of CMS integrations. Check version.json or config.php within the installation for version information.
    Affected if The installed version is exactly 2.7.6
  2. Verify the specific version
    Open the version file or check the header of core JavaScript files in the RichFilemanager directory. Common version file locations include /version.json, /js/version.js, or inspect the response headers from the application.
    Affected if The version returned is 2.7.6 exactly
  3. Confirm UploadHandler.php exists
    Check for the presence of /php/UploadHandler.php within the RichFilemanager installation directory. This file handles file upload operations.
    Affected if The file /php/UploadHandler.php exists and is accessible via the web server
  4. Test if upload functionality is enabled
    Attempt a test file upload through the web interface or directly to /php/UploadHandler.php to verify the upload endpoint is functional. Check the uploads directory permissions and configuration.
    Affected if Uploads can be processed and files are saved to a web-accessible directory
  5. Check uploads directory script execution
    Inspect the uploads directory configuration - look for .htaccess files, server configuration, or security settings that may prevent PHP or script execution. Verify if uploaded files retain executable extensions like .php.
    Affected if Uploaded files can be saved with executable extensions (such as .php) and the directory allows script execution

A system is affected if it runs RichFilemanager version 2.7.6 with the /php/UploadHandler.php component accessible and uploads can be saved with executable file types in a web-accessible location.

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

Implement strict server-side file type validation using magic bytes/file signatures, disable script execution in upload directories via .htaccess or web server config, apply content-disposition headers to force download, and upgrade to patched version if available.

Recommended fix Moderate confidence

Any stable release newer than 2.7.6 (check GitHub releases for 2.7.7 or later)

  1. 1. Navigate to the official RichFilemanager GitHub repository
  2. 2. Check the releases page for versions newer than 2.7.6
  3. 3. Identify the next available stable release that includes the security fix
  4. 4. Backup your current RichFilemanager installation
  5. 5. Download the new version from the official repository
  6. 6. Replace the existing files with the new version, preserving any custom configuration
  7. 7. Verify the UploadHandler.php component has been updated
  8. 8. Test file upload functionality to ensure normal operation
Caveat Review release notes for any configuration or feature changes between 2.7.6 and the target version

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

Fix this in Richfilemanager 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-2025-63994 — 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-2025-63994 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