# CVE-2022-37299: Path traversal in n/a

> Attackers can read arbitrary files from the server via a path traversal vulnerability in Shirne CMS.

- **Severity:** Medium 6.5 (`CVSS:3.1/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:** 9 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rg2q-2q6c-9x92

## What is CVE-2022-37299?

CVE-2022-37299 is a medium-severity path traversal vulnerability in n/a, published on 9 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Shirne CMS 1.2.0. There is a Path Traversal vulnerability which could cause arbitrary file read via /static/ueditor/php/controller.php

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

## Which versions are affected by CVE-2022-37299?

It affects 1 product.


Products: Shirne Cms Project Shirne Cms.

## How do I fix CVE-2022-37299?

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

## Is CVE-2022-37299 being exploited?

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

Public exploit code:

- Shirne CMS 1.2.0 - Local File Inclusion (nuclei): http/cves/2022/CVE-2022-37299.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37299 and fix it if it is affected.

What it is: CVE-2022-37299 is a medium-severity path traversal vulnerability in n/a, published on 9 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-37299 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-2022-37299/ (Markdown: https://insights.sbomify.com/CVE-2022-37299/index.md)
```

## Sources

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

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