CVE-2025-14522VulnerabilityPublished 11 Dec 2025

CVE-2025-14522: baowzh hfly · Unrestricted Upload

Affects baowzh hflySource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediately audit all instances of baowzh hfly to identify exposure of the /Public/Kindeditor/php/upload_json.php endpoint. 2. Implement strict access controls and network segmentation to limit exposure of vulnerable endpoints to trusted internal networks only. 3. Deploy web application firewalls (WAFs) with custom rules to detect and block suspicious file upload attempts targeting the imgFile parameter. 4. Conduct manual or automated code reviews to add server-side validation restricting file types, sizes, and content for uploads. 5. Disable or restrict file upload functionality if not essential. 6. Monitor logs for unusual upload activity or webshell deployment indicators. 7. If possible, replace or isolate the affected component until a vendor patch or update is available. 8. Engage in threat hunting to detect any signs of compromise related to this vulnerability. 9. Maintain up-to-date backups and incident response plans to quickly recover from potential exploitation. 10. Advocate for vendor engagement and monitor for any forthcoming patches or advisories.

Description

A vulnerability was detected in baowzh hfly up to 638ff9abe9078bc977c132b37acbe1900b63491c. The impacted element is an unknown function of the file /Public/Kindeditor/php/upload_json.php. Performing manipulation of the argument imgFile results in unrestricted upload. It is possible to initiate the attack remotely. The exploit is now public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized file uploads, enabling attackers to execute arbitrary code, implant backdoors, or manipulate data. This can compromise the confidentiality, integrity, and availability of affected systems, potentially leading to data breaches, service disruptions, or lateral movement within networks. Given the remote and unauthenticated nature of the exploit, attackers could target exposed instances at scale. Sectors relying on baowzh hfly for web content management or internal applications may face operational risks and reputational damage. The lack of vendor response and patches increases exposure duration, heightening the risk. Additionally, compliance with European data protection regulations (e.g., GDPR) could be jeopardized if personal data is compromised through exploitation. Organizations with internet-facing deployments of baowzh hfly are particularly vulnerable.

Summary

CVE-2025-14522 is a vulnerability identified in the baowzh hfly software, specifically affecting the file upload functionality implemented in /Public/Kindeditor/php/upload_json.php. The flaw arises from insufficient validation or restrictions on the imgFile parameter, which allows an attacker to upload arbitrary files, including potentially malicious scripts. This unrestricted upload can lead to remote code execution or unauthorized system access. The vulnerability is exploitable remotely without requiring authentication or user interaction, making it relatively easy to exploit. The product uses a rolling release model, complicating version tracking and patch management, and the vendor has not responded to disclosure efforts, leaving the vulnerability unpatched. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the network attack vector, lack of authentication, and low complexity, but limited impact on confidentiality, integrity, and availability. Although no active exploitation has been reported, the public availability of exploit code increases the risk of future attacks. Organizations running baowzh hfly should be aware of this vulnerability and take immediate steps to mitigate potential exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 11 Dec 2025, 16:38 UTC

Technical details

References

Community reviews

Related threats