# CVE-2023-25350: SQL injection in n/a

> Attackers can execute arbitrary SQL commands via the login form, potentially accessing or modifying database contents.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Mar 2023
- **Updated:** 21 Feb 2025
- **Also known as:** GHSA-qfr3-mfc8-5fjx

## What is CVE-2023-25350?

CVE-2023-25350 is a high-severity SQL injection vulnerability in n/a, published on 24 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Faveo Helpdesk 1.0-1.11.1 is vulnerable to SQL Injection. When the user logs in through the login box, he has no judgment on the validity of the user's input data. The parameters passed from the front end to the back end are controllable, which will lead to SQL injection.

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

## Which versions are affected by CVE-2023-25350?

It affects 1 product.


Products: Ladybirdweb Faveo Helpdesk.

## How do I fix CVE-2023-25350?

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

## Is CVE-2023-25350 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-51377](https://insights.sbomify.com/CVE-2024-51377/): Cross-site scripting in n/a (high 8.8)
- [CVE-2017-7571](https://insights.sbomify.com/CVE-2017-7571/): Cross-site request forgery in n/a (high 8.0)
- [CVE-2023-1724](https://insights.sbomify.com/CVE-2023-1724/): Faveo Helpdesk Enterprise 6.0.1 - Privilege Escalation via Stored XSS (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25350 and fix it if it is affected.

What it is: CVE-2023-25350 is a high-severity SQL injection vulnerability in n/a, published on 24 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-25350 in the wild and no public exploit code.

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-2023-25350/ (Markdown: https://insights.sbomify.com/CVE-2023-25350/index.md)
```

## Sources

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

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