# CVE-2005-0795: Path traversal in n/a

> Remote attackers can overwrite arbitrary files in HolaCMS by manipulating the vote_filename parameter due to unrestricted directory access.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 20 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rrfp-966g-v3mq

## What is CVE-2005-0795?

CVE-2005-0795 is a medium-severity path traversal vulnerability in n/a, published on 20 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HolaCMS 1.4.9 does not restrict file access to the holaDB/votes directory, which allows remote attackers to overwrite arbitrary files via a modified vote_filename parameter.

## Which versions are affected by CVE-2005-0795?

It affects 1 product.


Products: Hola Holacms.

## How do I fix CVE-2005-0795?

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

## Is CVE-2005-0795 being exploited?

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

Public exploit code:

- HolaCMS 1.2/1.4.x Voting Module - Remote File Corruption (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0795 and fix it if it is affected.

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

## Sources

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

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