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

> Remote attackers can execute arbitrary code or read sensitive files via Local File Inclusion in the Redbasic theme.

- **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:** 15 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7p22-9f27-w6fq

## What is CVE-2022-27257?

CVE-2022-27257 is a high-severity path traversal vulnerability in n/a, published on 15 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A PHP Local File Inclusion vulneraility in the default Redbasic theme for Hubzilla before version 7.2 allows remote attackers to include arbitrary php files via the schema parameter.

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

It affects 1 product.


Products: Hubzilla Hubzilla.

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

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

## Is CVE-2022-27257 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-27258](https://insights.sbomify.com/CVE-2022-27258/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2022-27256](https://insights.sbomify.com/CVE-2022-27256/): Path traversal in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27257 is a high-severity path traversal vulnerability in n/a, published on 15 Apr 2022. 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-2022-27257 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-2022-27257/ (Markdown: https://insights.sbomify.com/CVE-2022-27257/index.md)
```

## Sources

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

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