# CVE-2025-71428: Jivejdon through 5.0 SQL Injection via username in userListAction

> Authenticated administrators can inject SQL via the username parameter in Jivejdon to read database contents, including password hashes.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-824j-5w2g-7j65

## What is CVE-2025-71428?

CVE-2025-71428 is a medium-severity SQL injection vulnerability in banq jivejdon, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Jivejdon through 5.0 contains a sql injection vulnerability in AccountDaoSql.getAccountByNameLike() that allows authenticated administrators to inject SQL via the username parameter. Attackers with the Admin role can submit crafted input to /admin/user/userListAction to read database contents, including other accounts' password hashes.

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

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


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

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

## Is CVE-2025-71428 being exploited?

There is no known exploitation of CVE-2025-71428 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-71428 is a medium-severity SQL injection vulnerability in banq jivejdon, published on 8 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-71428 in the wild and no public exploit code.

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

## Sources

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

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