# CVE-2019-25099: Arthmoor QSF-Portal index.php path traversal

> Attackers can exploit a path traversal vulnerability in QSF-Portal to read arbitrary files from the server.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-2rwp-q9wg-42qm

## What is CVE-2019-25099?

CVE-2019-25099 is a medium-severity path traversal vulnerability in Arthmoor QSF-Portal, published on 6 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in Arthmoor QSF-Portal. This vulnerability affects unknown code of the file index.php. The manipulation of the argument a leads to path traversal. The patch is identified as ea4f61e23ecb83247d174bc2e2cbab521c751a7d. It is recommended to apply a patch to fix this issue. VDB-217558 is the identifier assigned to this vulnerability.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Afkmods Qsf-Portal.

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

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

## Is CVE-2019-25099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25099 is a medium-severity path traversal vulnerability in Arthmoor QSF-Portal, published on 6 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-25099 in the wild and no public exploit code.

Affected product: Arthmoor QSF-Portal. 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-25099/ (Markdown: https://insights.sbomify.com/CVE-2019-25099/index.md)
```

## Sources

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

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