# CVE-2024-8303: dingfanzu CMS getBasicInfo.php sql injection

> Remote attackers can exploit SQL injection in dingfanzu CMS to read or modify database contents via the username parameter.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA: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:** 29 Aug 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-p7q6-fc7h-j55q

## What is CVE-2024-8303?

CVE-2024-8303 is a medium-severity SQL injection vulnerability in dingfanzu CMS, published on 29 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in dingfanzu CMS up to 29d67d9044f6f93378e6eb6ff92272217ff7225c. This affects an unknown part of the file /ajax/getBasicInfo.php. The manipulation of the argument username leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2024-8303 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8303 is a medium-severity SQL injection vulnerability in dingfanzu CMS, published on 29 Aug 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-8303 exists.

Affected product: dingfanzu CMS. 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-8303/ (Markdown: https://insights.sbomify.com/CVE-2024-8303/index.md)
```

## Sources

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

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