# CVE-2026-37431: SQL injection in n/a

> Attackers can access sensitive database information via SQL injection in the appointment detail endpoint of the Beauty Parlour 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:** 8 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-fmp3-3p2g-4h8r

## What is CVE-2026-37431?

CVE-2026-37431 is a critical SQL injection vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Beauty Parlour Management System v1.1 was discovered to contain a SQL injection vulnerability via the aptnumber parameter in the /appointment-detail.php endpoint. This vulnerability allows attackers to access sensitive database information via a crafted SQL statement.

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

## Which versions are affected by CVE-2026-37431?


## How do I fix CVE-2026-37431?

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

## Is CVE-2026-37431 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37431 and fix it if it is affected.

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

## Sources

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

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