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

> Attackers can exploit SQL injection in Audimexee to read or modify database contents via the p_table_name parameter.

- **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:** 5 Sep 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-2jvx-42cx-5ggp

## What is CVE-2023-36361?

CVE-2023-36361 is a critical SQL injection vulnerability in n/a, published on 5 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Audimexee v14.1.7 was discovered to contain a SQL injection vulnerability via the p_table_name parameter.

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

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

It affects 1 product.


Products: Web-Audimex Audimexee.

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

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

## Is CVE-2023-36361 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28115](https://insights.sbomify.com/CVE-2020-28115/): SQL injection in n/a (high 8.8)
- [CVE-2023-39558](https://insights.sbomify.com/CVE-2023-39558/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-30889](https://insights.sbomify.com/CVE-2024-30889/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2020-28047](https://insights.sbomify.com/CVE-2020-28047/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2023-39559](https://insights.sbomify.com/CVE-2023-39559/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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