# CVE-2013-7095: XML external entity in n/a

> An XML External Entity vulnerability in SAP CRM allows attackers to potentially read sensitive data or cause denial of service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 13 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m44h-37m9-w5jw

## What is CVE-2013-7095?

CVE-2013-7095 is a critical vulnerability in n/a, published on 13 Dec 2013. 

### Official description

The XML parser (crm_flex_data) in SAP Customer Relationship Management (CRM) 7.02 EHP 2 has unknown impact and attack vectors related to an XML External Entity (XXE) issue.

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

It affects 1 product.


Products: Sap Customer Relationship Management.

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

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

## Is CVE-2013-7095 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-2380](https://insights.sbomify.com/CVE-2018-2380/): SAP Customer Relationship Management (CRM) Path Traversal (medium 6.6, exploited in the wild)
- [CVE-2014-8669](https://insights.sbomify.com/CVE-2014-8669/): Code injection in n/a (critical 10.0)
- [CVE-2017-15296](https://insights.sbomify.com/CVE-2017-15296/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2015-3979](https://insights.sbomify.com/CVE-2015-3979/): Code injection in n/a (high 7.5)
- [CVE-2015-3980](https://insights.sbomify.com/CVE-2015-3980/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7095 is a critical vulnerability in n/a, published on 13 Dec 2013. 
Exploitation: There is no known exploitation of CVE-2013-7095 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-7095/ (Markdown: https://insights.sbomify.com/CVE-2013-7095/index.md)
```

## Sources

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

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