# CVE-2020-35598: Path traversal in n/a

> Attackers can read arbitrary files from the server via directory traversal in ACS Advanced Comment System.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 23 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3896-fhmw-qp2v

## What is CVE-2020-35598?

CVE-2020-35598 is a high-severity path traversal vulnerability in n/a, published on 23 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ACS Advanced Comment System 1.0 is affected by Directory Traversal via an advanced_component_system/index.php?ACS_path=..%2f URI. NOTE: this might be the same as CVE-2009-4623

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

## Which versions are affected by CVE-2020-35598?

It affects 1 product.


Products: Advanced Comment System Project Advanced Comment System.

## How do I fix CVE-2020-35598?

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

## Is CVE-2020-35598 being exploited?

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

Public exploit code:

- Advanced Comment System 1.0 - 'ACS_path' Path Traversal (exploitdb)
- Advanced Comment System 1.0 - Local File Inclusion (nuclei): http/cves/2020/CVE-2020-35598.yaml

## Other vulnerabilities in n/a

- [CVE-2018-18619](https://insights.sbomify.com/CVE-2018-18619/): SQL injection in n/a (critical 9.8)
- [CVE-2018-18845](https://insights.sbomify.com/CVE-2018-18845/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-35598 and fix it if it is affected.

What it is: CVE-2020-35598 is a high-severity path traversal vulnerability in n/a, published on 23 Dec 2020. 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-2020-35598 exists.

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

## Sources

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

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