# CVE-2012-3838: Information disclosure in n/a

> Remote attackers can obtain the installation path by accessing specific template files, exposing sensitive server information.

- **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:** 3 Jul 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vfrc-j747-4j7p

## What is CVE-2012-3838?

CVE-2012-3838 is a medium-severity vulnerability in n/a, published on 3 Jul 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gekko before 1.2.0 allows remote attackers to obtain the installation path via a direct request to (1) admin/templates/babygekko/index.php or (2) templates/html5demo/index.php.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2012-3838?

It affects 1 product.


Products: Babygekko Baby Gekko.

## How do I fix CVE-2012-3838?

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

## Is CVE-2012-3838 being exploited?

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

Public exploit code:

- Baby Gekko CMS 1.1.5c - Multiple Persistent Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-5700](https://insights.sbomify.com/CVE-2012-5700/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-3836](https://insights.sbomify.com/CVE-2012-3836/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-3837](https://insights.sbomify.com/CVE-2012-3837/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3838 and fix it if it is affected.

What it is: CVE-2012-3838 is a medium-severity vulnerability in n/a, published on 3 Jul 2012. 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-2012-3838 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-2012-3838/ (Markdown: https://insights.sbomify.com/CVE-2012-3838/index.md)
```

## Sources

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

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