# CVE-2023-27510: Information disclosure in JB Inquiry form

> Remote unauthenticated attackers can access private personal information submitted through JB Inquiry forms.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2023
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-g3x7-rm82-3mw8

## What is CVE-2023-27510?

CVE-2023-27510 is a medium-severity vulnerability in Jubei Inc. JB Inquiry form, published on 10 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JB Inquiry form contains an exposure of private personal information to an unauthorized actor vulnerability, which may allow a remote unauthenticated attacker to obtain information entered from forms created using the affected product. The affected products and versions are as follows: JB Inquiry form versions 0.6.1 and 0.6.0, JB Inquiry form versions 0.5.2, 0.5.1 and 0.5.0, and JB Inquiry form version 0.40.

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

It affects 1 product.


Products: Jubei Jb Inquiry Form.

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

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

## Is CVE-2023-27510 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27510 is a medium-severity vulnerability in Jubei Inc. JB Inquiry form, published on 10 May 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-27510 in the wild and no public exploit code.

Affected product: Jubei Inc. JB Inquiry form. 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-27510/ (Markdown: https://insights.sbomify.com/CVE-2023-27510/index.md)
```

## Sources

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

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