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

> An attacker can exploit a SQL injection vulnerability in the user registration portal to read or modify database contents.

- **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:** 21 Aug 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-jv2j-mm55-5fw8

## What is CVE-2023-39807?

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

### Official description

N.V.K.INTER CO., LTD. (NVK) iBSG v3.5 was discovered to contain a SQL injection vulnerability via the a_passwd parameter at /portal/user-register.php.

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

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

It affects 1 product.


Products: Nvki Intelligent Broadband Subscriber Gateway.

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

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

## Is CVE-2023-39807 being exploited?

There is no known exploitation of CVE-2023-39807 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-39808](https://insights.sbomify.com/CVE-2023-39808/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2023-39809](https://insights.sbomify.com/CVE-2023-39809/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39807 is a critical SQL injection vulnerability in n/a, published on 21 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-39807 in the wild and no public exploit code.

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-39807/ (Markdown: https://insights.sbomify.com/CVE-2023-39807/index.md)
```

## Sources

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

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