# CVE-2010-1267: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in WebMaid CMS, exposing sensitive data without authentication.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 6 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mwq3-xvpm-p7v3

## What is CVE-2010-1267?

CVE-2010-1267 is a medium-severity path traversal vulnerability in n/a, published on 6 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in WebMaid CMS 0.2-6 Beta and earlier allow remote attackers to read arbitrary files via directory traversal sequences in the com parameter to (1) cContactus.php, (2) cGuestbook.php, and (3) cArticle.php.

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

## Which versions are affected by CVE-2010-1267?

It affects 1 product.


Products: Kjetiltroan Webmaid Cms.

## How do I fix CVE-2010-1267?

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

## Is CVE-2010-1267 being exploited?

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

Public exploit code:

- WebMaid CMS 0.2-6 Beta - Multiple Remote File Inclusions (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-1266](https://insights.sbomify.com/CVE-2010-1266/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1267 and fix it if it is affected.

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

## Sources

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

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