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

> Attackers can exploit SQL injection in AutoCMS admin panel to read or modify database contents.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2024
- **Updated:** 9 Sep 2024
- **Also known as:** GHSA-rpgh-j58g-qrc4

## What is CVE-2024-44725?

CVE-2024-44725 is a high-severity SQL injection vulnerability in n/a, published on 9 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

AutoCMS v5.4 was discovered to contain a SQL injection vulnerability via the sidebar parameter at /admin/robot.php.

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

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

It affects 1 product.


Products: Autocms Project Autocms.

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

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

## Is CVE-2024-44725 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-44724](https://insights.sbomify.com/CVE-2024-44724/): Code injection in n/a (high 7.2)
- [CVE-2024-8866](https://insights.sbomify.com/CVE-2024-8866/): AutoCMS robot.php cross site scripting (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44725 is a high-severity SQL injection vulnerability in n/a, published on 9 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44725 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-44725/ (Markdown: https://insights.sbomify.com/CVE-2024-44725/index.md)
```

## Sources

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

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