# CVE-2013-0939: Information disclosure in n/a

> Remote attackers can obtain sensitive information via cross-origin frame navigation in EMC Documentum Webtop and related components.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7rhx-5frh-x32w

## What is CVE-2013-0939?

CVE-2013-0939 is a medium-severity vulnerability in n/a, published on 10 May 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

EMC Documentum Webtop before 6.7 SP2, Documentum WDK before 6.7 SP2, Documentum Taskspace before 6.7 SP2, and Documentum Records Manager before 6.7 SP2 allow remote attackers to obtain sensitive information via vectors involving cross-origin frame navigation, related to a "Cross Frame Scripting" issue.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-0939?

It affects 4 products.


Products: Emc Documentum Records Manager, Emc Documentum Taskspace, Emc Documentum Wdk, Emc Documentum Webtop.

## How do I fix CVE-2013-0939?

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

## Is CVE-2013-0939 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0937](https://insights.sbomify.com/CVE-2013-0937/): Auth bypass in n/a (medium 5.8)
- [CVE-2013-0938](https://insights.sbomify.com/CVE-2013-0938/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0939 and fix it if it is affected.

What it is: CVE-2013-0939 is a medium-severity vulnerability in n/a, published on 10 May 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-0939 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-2013-0939/ (Markdown: https://insights.sbomify.com/CVE-2013-0939/index.md)
```

## Sources

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

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