# CVE-2025-4909: SourceCodester Client Database Management System exposure of information through directory listing

> Remote attackers can access sensitive files via directory listing in SourceCodester Client Database Management System.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2025
- **Updated:** 19 May 2025
- **Also known as:** GHSA-7gvx-rvmq-cw57

## What is CVE-2025-4909?

CVE-2025-4909 is a medium-severity vulnerability in SourceCodester Client Database Management System, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as critical was found in SourceCodester Client Database Management System 1.0. This vulnerability affects unknown code. The manipulation leads to exposure of information through directory listing. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-548 (Exposure of Information Through Directory Listing)

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

It affects 1 product.


Products: Lerouxyxchire Client Database Management System.

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

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

## Is CVE-2025-4909 being exploited?

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

## Other vulnerabilities in SourceCodester Client Database Management System

- [CVE-2025-46188](https://insights.sbomify.com/CVE-2025-46188/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46189](https://insights.sbomify.com/CVE-2025-46189/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46190](https://insights.sbomify.com/CVE-2025-46190/): SQL injection in n/a (critical 9.8)
- [CVE-2025-46191](https://insights.sbomify.com/CVE-2025-46191/): File upload in n/a (critical 9.8)
- [CVE-2025-46192](https://insights.sbomify.com/CVE-2025-46192/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4909 is a medium-severity vulnerability in SourceCodester Client Database Management System, published on 19 May 2025. 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-4909 exists.

Affected product: SourceCodester Client Database 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-2025-4909/ (Markdown: https://insights.sbomify.com/CVE-2025-4909/index.md)
```

## Sources

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

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