# CVE-2019-25713: MyT-PM 1.5.1 SQL Injection via Charge[group_total] Parameter

> Authenticated attackers can execute arbitrary SQL queries via the Charge[group_total] parameter to extract or manipulate database information.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-m5v5-2jv8-fp63

## What is CVE-2019-25713?

CVE-2019-25713 is a high-severity SQL injection vulnerability in MyT Project Management, published on 12 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MyT-PM 1.5.1 contains an SQL injection vulnerability that allows authenticated attackers to execute arbitrary SQL queries by injecting malicious code through the Charge[group_total] parameter. Attackers can submit crafted POST requests to the /charge/admin endpoint with error-based, time-based blind, or stacked query payloads to extract sensitive database information or manipulate data.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-25713?

It affects 1 product.


Products: Myt Project Myt.

## How do I fix CVE-2019-25713?

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

## Is CVE-2019-25713 being exploited?

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

## Other vulnerabilities in MyT Project Management

- [CVE-2019-13346](https://insights.sbomify.com/CVE-2019-13346/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25713 and fix it if it is affected.

What it is: CVE-2019-25713 is a high-severity SQL injection vulnerability in MyT Project Management, published on 12 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25713 exists.

Affected product: MyT Project Management. 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-2019-25713/ (Markdown: https://insights.sbomify.com/CVE-2019-25713/index.md)
```

## Sources

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

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