# CVE-2023-43013: Asset Management System v1.0 - Unauthenticated SQL Injection (SQLi)

> An unauthenticated attacker can exploit SQL injection to dump database contents and bypass login controls in the Asset Management System.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2023
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-4fv5-wjqm-7f2r

## What is CVE-2023-43013?

CVE-2023-43013 is a critical SQL injection vulnerability in Asset Management System, published on 28 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Asset Management System v1.0 is vulnerable to an

unauthenticated SQL Injection vulnerability on the

'email' parameter of index.php page, allowing an

external attacker to dump all the contents of the

database contents and bypass the login control.

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

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

It affects 1 product.


Products: Projectworlds Asset Management System.

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

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

## Is CVE-2023-43013 being exploited?

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

## Other vulnerabilities in Asset Management System

- [CVE-2023-43014](https://insights.sbomify.com/CVE-2023-43014/): Asset Management System v1.0 - Authenticated SQL Injection (SQLi) (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43013 is a critical SQL injection vulnerability in Asset Management System, published on 28 Sep 2023. 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-2023-43013 exists.

Affected product: Asset Management System. 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-43013/ (Markdown: https://insights.sbomify.com/CVE-2023-43013/index.md)
```

## Sources

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

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