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

> Remote attackers can obtain the installation path via the Media Upload form in the Video Embed & Thumbnail Generator plugin.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xhmg-vv82-6q8v

## What is CVE-2012-1786?

CVE-2012-1786 is a medium-severity vulnerability in n/a, published on 19 Mar 2012. It can be exploited over the network, with no action from the victim.

### Official description

The Media Upload form in the Video Embed & Thumbnail Generator plugin before 2.0 for WordPress allows remote attackers to obtain the installation path via unknown vectors.

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

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

It affects 1 product.


Products: Kylegilman Video Embed \& Thumbnail Generator.

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

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

## Is CVE-2012-1786 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1785](https://insights.sbomify.com/CVE-2012-1785/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1786 is a medium-severity vulnerability in n/a, published on 19 Mar 2012. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1786 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-2012-1786/ (Markdown: https://insights.sbomify.com/CVE-2012-1786/index.md)
```

## Sources

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

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