# CVE-2018-20646: Path traversal in n/a

> Attackers can access restricted directories by requesting image listings, exposing sensitive files in PHP Scripts Mall Basic B2B Script.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 20 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m4rh-gx48-v325

## What is CVE-2018-20646?

CVE-2018-20646 is a medium-severity path traversal vulnerability in n/a, published on 20 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PHP Scripts Mall Basic B2B Script 2.0.9 has has directory traversal via a direct request for a listing of an image directory such as an uploads/ directory.

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

## Which versions are affected by CVE-2018-20646?

It affects 1 product.


Products: Basic B2b Script Project Basic B2b Script.

## How do I fix CVE-2018-20646?

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

## Is CVE-2018-20646 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17600](https://insights.sbomify.com/CVE-2017-17600/): SQL injection in n/a (critical 9.8)
- [CVE-2018-20644](https://insights.sbomify.com/CVE-2018-20644/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-20645](https://insights.sbomify.com/CVE-2018-20645/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20646 and fix it if it is affected.

What it is: CVE-2018-20646 is a medium-severity path traversal vulnerability in n/a, published on 20 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20646 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-2018-20646/ (Markdown: https://insights.sbomify.com/CVE-2018-20646/index.md)
```

## Sources

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

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