# CVE-2024-3621: SourceCodester Kortex Lite Advocate Office Management System register_case.php sql injection

> Remote attackers can exploit SQL injection in register_case.php to read or modify database contents in Kortex Lite Advocate Office Management System.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-jqqv-px8m-v953

## What is CVE-2024-3621?

CVE-2024-3621 is a medium-severity SQL injection vulnerability in SourceCodester Kortex Lite Advocate Office Management System, published on 11 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in SourceCodester Kortex Lite Advocate Office Management System 1.0. It has been classified as critical. This affects an unknown part of the file /control/register_case.php. The manipulation of the argument title/case_no/client_name/court/case_type/case_stage/legel_acts/description/filling_date/hearing_date/opposite_lawyer/total_fees/unpaid leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-260277 was assigned to this vulnerability.

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

## Which versions are affected by CVE-2024-3621?

It affects 1 product.


Products: Mayurik Advocate Office Management System.

## How do I fix CVE-2024-3621?

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

## Is CVE-2024-3621 being exploited?

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

## Other vulnerabilities in SourceCodester Kortex Lite Advocate Office Management System

- [CVE-2024-9295](https://insights.sbomify.com/CVE-2024-9295/): SourceCodester Advocate Office Management System login.php sql injection (medium 6.9)
- [CVE-2024-9296](https://insights.sbomify.com/CVE-2024-9296/): SourceCodester Advocate Office Management System forgot_pass.php sql injection (medium 6.9)
- [CVE-2025-2626](https://insights.sbomify.com/CVE-2025-2626/): SourceCodester Kortex Lite Advocate Office Management System edit_case.php sql injection (medium 5.3)
- [CVE-2025-2601](https://insights.sbomify.com/CVE-2025-2601/): SourceCodester Kortex Lite Advocate Office Management System activate_reg.php sql injection (medium 5.3)
- [CVE-2025-2602](https://insights.sbomify.com/CVE-2025-2602/): SourceCodester Kortex Lite Advocate Office Management System deactivate_reg.php sql injection (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3621 and fix it if it is affected.

What it is: CVE-2024-3621 is a medium-severity SQL injection vulnerability in SourceCodester Kortex Lite Advocate Office Management System, published on 11 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3621 exists.

Affected product: SourceCodester Kortex Lite Advocate Office Management System. 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-2024-3621/ (Markdown: https://insights.sbomify.com/CVE-2024-3621/index.md)
```

## Sources

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

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