# CVE-2019-5725: Server-side request forgery in n/a

> Remote attackers can exploit Server-Side Request Forgery in Qibosoft to read arbitrary files, including sensitive database dumps, via the member index parameter.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 8 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-544h-w96w-xp69

## What is CVE-2019-5725?

CVE-2019-5725 is a high-severity server-side request forgery vulnerability in n/a, published on 8 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

qibosoft through V7 allows remote attackers to read arbitrary files via the member/index.php main parameter, as demonstrated by SSRF to a URL on the same web site to read a .sql file.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2019-5725?

It affects 1 product.


Products: Qibosoft Qibosoft.

## How do I fix CVE-2019-5725?

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

## Is CVE-2019-5725 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17613](https://insights.sbomify.com/CVE-2019-17613/): Code injection in n/a (critical 9.8)
- [CVE-2020-20944](https://insights.sbomify.com/CVE-2020-20944/): Path traversal in n/a (critical 9.1)
- [CVE-2020-20945](https://insights.sbomify.com/CVE-2020-20945/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-18201](https://insights.sbomify.com/CVE-2018-18201/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2021-27811](https://insights.sbomify.com/CVE-2021-27811/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5725 and fix it if it is affected.

What it is: CVE-2019-5725 is a high-severity server-side request forgery vulnerability in n/a, published on 8 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5725 in the wild and no public exploit code.

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-2019-5725/ (Markdown: https://insights.sbomify.com/CVE-2019-5725/index.md)
```

## Sources

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

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