# CVE-2024-22856: SQL injection in n/a

> Authenticated attackers can execute SQL queries via the Save Favorite Search function to disclose sensitive database information.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 22 Apr 2024
- **Updated:** 22 Nov 2024
- **Also known as:** GHSA-c4j4-3j3p-cjc9

## What is CVE-2024-22856?

CVE-2024-22856 is a medium-severity SQL injection vulnerability in n/a, published on 22 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A SQL injection vulnerability via the Save Favorite Search function in Axefinance Axe Credit Portal >= v.3.0 allows authenticated attackers to execute unintended queries and disclose sensitive information from DB tables via crafted requests.

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

## Which versions are affected by CVE-2024-22856?


## How do I fix CVE-2024-22856?

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

## Is CVE-2024-22856 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22856 and fix it if it is affected.

What it is: CVE-2024-22856 is a medium-severity SQL injection vulnerability in n/a, published on 22 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22856 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-2024-22856/ (Markdown: https://insights.sbomify.com/CVE-2024-22856/index.md)
```

## Sources

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

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