dbcve.org
HflyApplication · Baowzh

CVE-2025-14521

HIGH · 7.5 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to after 2016-05-11 or later.
See remediation →
84/100
Remediation priority · High
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 security vulnerability has been detected in baowzh hfly up to 638ff9abe9078bc977c132b37acbe1900b63491c. The affected element is an unknown function of the file /admin/index.php/datafile/download. Such manipulation of the argument filename leads to path traversal. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. 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 · high confidence

A path traversal vulnerability exists in baowzh hfly's /admin/index.php/datafile/download endpoint. The filename parameter is not properly validated, allowing attackers to use directory traversal sequences (e.g., ../../) to access arbitrary files on the server filesystem. This is a high-severity issue as it can be exploited remotely without authentication.

MitigationImplement strict input validation on the filename parameter, restricting it to expected values and using realpath() or equivalent to verify the resolved path stays within an allowed directory. Disable directory traversal sequence processing and validate against a whitelist of permitted files.

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

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

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 baowzh hfly installation
    Search the server for files or directories related to baowzh hfly or hfly application. Look for web root directories containing 'hfly' or 'baowzh' in the path, or check running web services for baowzh hfly responses.
    Affected if baowzh hfly software is installed on the server
  2. Determine installed version
    Locate any version information for the baowzh hfly installation. Check application configuration files, headers, or footer files for build or release dates. Compare the version or date to the affected range ( <= 2016-05-11).
    Affected if The installed version is dated 2016-05-11 or earlier, or version cannot be determined but falls within the affected range
  3. Verify vulnerable endpoint exists
    Check if the /admin/index.php/datafile/download endpoint is accessible on the server. This may require HTTP access to the application's admin path.
    Affected if The /admin/index.php/datafile/download endpoint is present and responds to requests
  4. Test filename parameter for path traversal
    Send a test request to the /admin/index.php/datafile/download endpoint with a directory traversal sequence in the filename parameter (e.g., filename=../../somefile). Observe if the application returns files outside the intended directory.
    Affected if The endpoint accepts directory traversal sequences and returns arbitrary files from the server filesystem

A user is affected if baowzh hfly version 2016-05-11 or earlier is installed and the /admin/index.php/datafile/download endpoint is accessible and allows path traversal in the filename parameter.

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 on the filename parameter, restricting it to expected values and using realpath() or equivalent to verify the resolved path stays within an allowed directory. Disable directory traversal sequence processing and validate against a whitelist of permitted files.

Fix this in Hfly Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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