Unrestricted File UploadWeakness · CWE-434

CVE-2025-26892

CRITICAL · 9.9 CVSS v3.1 Published 2025-05-19
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
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
Unrestricted Upload of File with Dangerous Type vulnerability in dkszone Celestial Aura allows Using Malicious Files.This issue affects Celestial Aura: from n/a through 2.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 · moderate confidence

A critical unrestricted file upload vulnerability in dkszone Celestial Aura (versions up to 2.2) allows attackers to upload malicious file types without validation, potentially enabling remote code execution by uploading executable files (e.g., PHP, JSP, ASP) that can then be accessed and executed on the server.

MitigationImplement strict allowlist-based file type validation on both client and server sides, verify file content/magic bytes rather than just extensions, store uploads outside webroot, rename uploaded files, and disable script execution in upload directories.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 dkszone Celestial Aura installation
    Search the system for Celestial Aura application files, check for installed packages, or look for the application in common web directories (e.g., /var/www/, /opt/, C:\inetpub\). Review any software inventory or application listings.
    Affected if The application is present on the system and handles file uploads.
  2. Determine installed version
    Locate version information - check application configuration files, about pages, or any version metadata files included with the installation. Compare the found version to the affected range (versions up to and including 2.2).
    Affected if The installed version is 2.2 or lower.
  3. Verify file upload feature is enabled
    Locate the application's configuration files and look for upload-related settings. Check the web interface for file upload functionality. Inspect the application's routing or endpoint configuration for upload handlers.
    Affected if File upload functionality is present and accessible to users.
  4. Inspect server-side file type validation
    Examine the application's source code, configuration, or web server settings for file upload validation logic. Look for file type allowlists or denylists, magic byte validation, or content-type checks in the upload handling code.
    Affected if No server-side file type validation exists, or validation relies solely on client-side checks or file extension matching without content verification.
  5. Check upload directory configuration
    Review the web server and application configuration to determine where uploaded files are stored. Verify if the upload directory is within the webroot and whether script execution is disabled in that location.
    Affected if Uploaded files are stored within the webroot and can be directly accessed/executed via HTTP requests.

The environment is affected if dkszone Celestial Aura version 2.2 or lower is installed with its file upload feature enabled and without proper server-side file type validation, especially if the upload directory is web-accessible.

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-based file type validation on both client and server sides, verify file content/magic bytes rather than just extensions, store uploads outside webroot, rename uploaded files, and disable script execution in upload directories.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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