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

> Authenticated attackers can exploit SQL injection in the member addition function 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:** 17 Feb 2023
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-26c3-c3ww-r8vj

## What is CVE-2023-23007?

CVE-2023-23007 is a high-severity SQL injection vulnerability in n/a, published on 17 Feb 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in ESPCMS P8.21120101 after logging in to the background, there is a SQL injection vulnerability in the function node where members are added.

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

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

It affects 1 product.


Products: Ecisp Espcms.

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

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

## Is CVE-2023-23007 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-44087](https://insights.sbomify.com/CVE-2022-44087/): Code injection in n/a (critical 9.8)
- [CVE-2022-44088](https://insights.sbomify.com/CVE-2022-44088/): Code injection in n/a (critical 9.8)
- [CVE-2022-44089](https://insights.sbomify.com/CVE-2022-44089/): Code injection in n/a (critical 9.8)
- [CVE-2020-18404](https://insights.sbomify.com/CVE-2020-18404/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23007 is a high-severity SQL injection vulnerability in n/a, published on 17 Feb 2023. 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-2023-23007 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-2023-23007/ (Markdown: https://insights.sbomify.com/CVE-2023-23007/index.md)
```

## Sources

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

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