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

> Remote attackers can execute arbitrary code via SQL injection in the orderby parameter of the money-pos system.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** 7 Nov 2025
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-3xhw-hf92-cgv2

## What is CVE-2025-63689?

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

### Official description

Multiple SQL injection vulnerabilitites in ycf1998 money-pos system before commit 11f276bd20a41f089298d804e43cb1c39d041e59 (2025-09-14) allows a remote attacker to execute arbitrary code via the orderby parameter

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

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

It affects 1 product.


Products: Ycf1998 Money-Pos.

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

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

## Is CVE-2025-63689 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63689 is a critical SQL injection vulnerability in n/a, published on 7 Nov 2025. 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-63689 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-63689/ (Markdown: https://insights.sbomify.com/CVE-2025-63689/index.md)
```

## Sources

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

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