# CVE-2025-57529: SQL injection in n/a

> Remote unauthenticated attackers can execute arbitrary SQL commands via crafted input, leading to unauthorized data access in the CPAS Audit Management System.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-g296-jp3g-x877

## What is CVE-2025-57529?

CVE-2025-57529 is a critical SQL injection vulnerability in n/a, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

YouDataSum CPAS Audit Management System <=v4.9 is vulnerable to SQL Injection in /cpasList/findArchiveReportByDah due to insufficient input validation. This allows remote unauthenticated attackers to execute arbitrary SQL commands via crafted input to the parameter. Successful exploitation could lead to unauthorized data access

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

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

It affects 1 product.


Products: Youdatasum Cpas Audit Management System.

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

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

## Is CVE-2025-57529 being exploited?

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

Public exploit code:

- CPAS audit management information system has SQL injection vulnerability(CVE-2025-57529) (github_poc): https://github.com/songqb-xx/CVE-2025-57529

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57529 is a critical SQL injection vulnerability in n/a, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57529 exists.

Affected product: n/a. 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-57529/ (Markdown: https://insights.sbomify.com/CVE-2025-57529/index.md)
```

## Sources

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

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