dbcve.org
Documentum Records ManagerApplication · Emc

CVE-2013-0939

MEDIUM · 5.8 CVSS v2.0 Published 2013-05-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross Frame Scripting (XFS) vulnerability in EMC Documentum Webtop, WDK, Taskspace, and Records Manager allows remote attackers to embed the application in frames on malicious websites and use cross-origin frame navigation to access sensitive information, potentially stealing session data or authentication credentials.

MitigationUpgrade affected Documentum products to version 6.7 SP2 or later to resolve the cross-frame scripting vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Documentum Records ManagerApplication
Affected:= 6.7
Documentum TaskspaceApplication
Affected:= 6.7
Documentum WdkApplication
Affected:= 6.7
Documentum WebtopApplication
Affected:= 6.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Documentum components
    Review the installed applications on the Documentum server and check for presence of Webtop, WDK, Taskspace, or Records Manager. These are typically installed in the Documentum installation directory. Use system inventory tools or check the application server (typically JBoss or WebLogic) for deployed Documentum web applications.
    Affected if Any of the four affected components (Webtop, WDK, Taskspace, Records Manager) are installed and accessible via web interface.
  2. Check Documentum product version
    Locate the version file or check the about dialog within each Documentum component. For Webtop, this is typically found in the webtop.war or in the installation directory. Check the version.properties file or examine the component version information in the Documentum Administration console.
    Affected if The installed version is exactly 6.7 or any version prior to 6.7 SP2.
  3. Verify if web interface is accessible
    Confirm the webtop or taskspace URL is accessible from a browser. Try accessing the typical endpoints such as /webtop or /taskspace on the Documentum application server port.
    Affected if The web interface is exposed and reachable, making the XFS attack surface viable.
  4. Check for X-Frame-Options header
    Use browser developer tools or a command-line tool like curl to inspect HTTP response headers from the Documentum web interface. Run: curl -I <documentum_url> and look for X-Frame-Options header.
    Affected if The X-Frame-Options header is absent from HTTP responses, allowing the application to be embedded in frames.
  5. Check for frame-breaking script
    View the HTML source of the Documentum login page and main application pages. Look for JavaScript that attempts to break out of frames (e.g., code checking if window.self !== window.top).
    Affected if No frame-breaking JavaScript is present in the application pages.

The environment is affected if any of Webtop, WDK, Taskspace, or Records Manager version 6.7 is installed and accessible without X-Frame-Options headers or frame-breaking scripts to prevent cross-frame scripting.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade affected Documentum products to version 6.7 SP2 or later to resolve the cross-frame scripting vulnerability.

Fix this in Documentum Records Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0939 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0939 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data