# CVE-2025-12329: shawon100 RUET OJ details.php sql injection

> Remote attackers can exploit SQL injection in details.php to read or modify database contents in the RUET OJ web application.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-p598-ccq9-3xq4

## What is CVE-2025-12329?

CVE-2025-12329 is a medium-severity SQL injection vulnerability in shawon100 RUET OJ, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in shawon100 RUET OJ up to 18fa45b0a669fa1098a0b8fc629cf6856369d9a5. The affected element is an unknown function of the file /details.php. Performing manipulation of the argument ID results in sql injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be exploited. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Shawonruet Ruet Oj.

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

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

## Is CVE-2025-12329 being exploited?

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

## Other vulnerabilities in shawon100 RUET OJ

- [CVE-2025-12326](https://insights.sbomify.com/CVE-2025-12326/): shawon100 RUET OJ POST Request process.php sql injection (medium 6.9)
- [CVE-2025-12327](https://insights.sbomify.com/CVE-2025-12327/): shawon100 RUET OJ description.php sql injection (medium 5.3)
- [CVE-2025-12328](https://insights.sbomify.com/CVE-2025-12328/): shawon100 RUET OJ contestproblem.php sql injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12329 is a medium-severity SQL injection vulnerability in shawon100 RUET OJ, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12329 in the wild and no public exploit code.

Affected product: shawon100 RUET OJ. 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-12329/ (Markdown: https://insights.sbomify.com/CVE-2025-12329/index.md)
```

## Sources

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

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