# CVE-2025-51567: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via POST parameters to gain unauthorized database access in the Online Exam System.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 12 Jan 2026
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-xfhq-47hp-mvcx

## What is CVE-2025-51567?

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

### Official description

A SQL Injection was found in the /exam/user/profile.php page of kashipara Online Exam System V1.0, which allows remote attackers to execute arbitrary SQL command to get unauthorized database access via the rname, rcollage, rnumber, rgender and rpassword parameters in a POST HTTP request.

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

## Which versions are affected by CVE-2025-51567?

It affects 1 product.


Products: Jayesh Online Exam System.

## How do I fix CVE-2025-51567?

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

## Is CVE-2025-51567 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-40480](https://insights.sbomify.com/CVE-2024-40480/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-40479](https://insights.sbomify.com/CVE-2024-40479/): SQL injection in n/a (high 8.1)
- [CVE-2024-40478](https://insights.sbomify.com/CVE-2024-40478/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-51567 and fix it if it is affected.

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

## Sources

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

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