dbcve.org
HflyApplication · Baowzh

CVE-2025-14520

CRITICAL · 9.1 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2016-05-11 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
A weakness has been identified in baowzh hfly up to 638ff9abe9078bc977c132b37acbe1900b63491c. Impacted is an unknown function of the file /admin/index.php/datafile/delfile. This manipulation of the argument filename causes path traversal. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited. This product adopts a rolling release strategy to maintain continuous delivery 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

Path traversal vulnerability in baowzh hfly's /admin/index.php/datafile/delfile endpoint allows remote attackers to delete arbitrary files by manipulating the 'filename' parameter with directory traversal sequences (e.g., ../../../'). The vulnerability stems from insufficient input validation on the filename argument before performing file operations.

MitigationImplement strict input validation using allowlists for permitted file paths, normalize file paths with realpath() to resolve traversal sequences, and verify the final resolved path remains within the intended directory before deletion.

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
HflyApplication
Affected:<= 2016-05-11

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm Baowzh Hfly is installed
    Locate the application's web root directory and identify if it contains files consistent with Baowzh Hfly. Look for index.php, admin directory, or application-specific configuration files.
    Affected if The application is Baowzh Hfly and was released on or before 2016-05-11
  2. Check the installed version
    Locate version information in the application's source code, configuration files, or any version indication files (such as version.php, about.php, or a README file). Compare the found version date to 2016-05-11.
    Affected if The installed version is dated 2016-05-11 or earlier
  3. Verify the vulnerable endpoint exists
    Check if /admin/index.php/datafile/delfile path exists by inspecting the application's directory structure, particularly under the /admin/ directory. Look for a datafile controller or module that handles file deletion operations.
    Affected if The /admin/index.php/datafile/delfile endpoint exists in the application
  4. Confirm the filename parameter is handled without validation
    Examine the delfile function code in the datafile module. Look for the 'filename' parameter handling and check whether directory traversal sequences (../) are validated or stripped before use in file operations.
    Affected if The filename parameter accepts raw user input and uses it directly in file deletion operations without proper path normalization or validation

You are affected if Baowzh Hfly version 2016-05-11 or earlier is installed and the /admin/index.php/datafile/delfile endpoint exists with the vulnerable filename parameter handling.

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
Upgrade available Upgrade to a release after 2016-05-11
Interim mitigation

Implement strict input validation using allowlists for permitted file paths, normalize file paths with realpath() to resolve traversal sequences, and verify the final resolved path remains within the intended directory before deletion.

Fix this in Hfly Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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