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

> Remote attackers can execute arbitrary SQL queries via the lead_id parameter, leading to database enumeration and potential full database compromise.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2025
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-f64q-6vqx-982f

## What is CVE-2025-56450?

CVE-2025-56450 is a medium-severity SQL injection vulnerability in n/a, published on 21 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Log2Space Subscriber Management Software 1.1 is vulnerable to unauthenticated SQL injection via the `lead_id` parameter in the `/l2s/api/selfcareLeadHistory` endpoint. A remote attacker can exploit this by sending a specially crafted POST request, resulting in the execution of arbitrary SQL queries. The backend fails to sanitize the user input, allowing enumeration of database schemas, table names, and potentially leading to full database compromise.

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

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


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

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

## Is CVE-2025-56450 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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