# CVE-2007-1127: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in ShopKitPlus, exposing sensitive data.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xwh4-f34j-qf9r

## What is CVE-2007-1127?

CVE-2007-1127 is a medium-severity path traversal vulnerability in n/a, published on 27 Feb 2007. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in enc/stylecss.php in shopkitplus allows remote attackers to read arbitrary files via a .. (dot dot) in the changetheme parameter.

## Which versions are affected by CVE-2007-1127?

It affects 1 product.


Products: Watersweb Shops Shop Kit Plus.

## How do I fix CVE-2007-1127?

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

## Is CVE-2007-1127 being exploited?

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

Public exploit code:

- Shop Kit Plus - 'StyleCSS.php' Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-1128](https://insights.sbomify.com/CVE-2007-1128/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1127 and fix it if it is affected.

What it is: CVE-2007-1127 is a medium-severity path traversal vulnerability in n/a, published on 27 Feb 2007. It can be exploited 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-2007-1127 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-2007-1127/ (Markdown: https://insights.sbomify.com/CVE-2007-1127/index.md)
```

## Sources

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

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