# CVE-2025-14519: baowzh hfly advtext add cross site scripting

> Remote attackers can inject malicious scripts into the advtext module, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-mv84-v97v-mj5f

## What is CVE-2025-14519?

CVE-2025-14519 is a medium-severity cross-site scripting vulnerability in baowzh hfly, published on 11 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A security flaw has been discovered in baowzh hfly up to 638ff9abe9078bc977c132b37acbe1900b63491c. This issue affects some unknown processing of the file /admin/index.php/advtext/add of the component advtext Module. The manipulation results in cross site scripting. The attack can be executed remotely. The exploit has been released to the public and may be exploited. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-14519?

It affects 1 product.


Products: Baowzh Hfly.

## How do I fix CVE-2025-14519?

No fix has been published for CVE-2025-14519 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14519 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14519 exists.

## Other vulnerabilities in baowzh hfly

- [CVE-2025-14520](https://insights.sbomify.com/CVE-2025-14520/): baowzh hfly delfile path traversal (medium 5.3)
- [CVE-2025-14521](https://insights.sbomify.com/CVE-2025-14521/): baowzh hfly download path traversal (medium 5.3)
- [CVE-2025-14522](https://insights.sbomify.com/CVE-2025-14522/): baowzh hfly upload_json.php unrestricted upload (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14519 and fix it if it is affected.

What it is: CVE-2025-14519 is a medium-severity cross-site scripting vulnerability in baowzh hfly, published on 11 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14519 exists.

Affected product: baowzh hfly. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14519/ (Markdown: https://insights.sbomify.com/CVE-2025-14519/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14519
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14519
- OSV: https://osv.dev/vulnerability/CVE-2025-14519

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14519/
Summaries are generated and may contain mistakes; the official description above is the record.
