# CVE-2015-6011: XML external entity in n/a

> Remote attackers can exploit XML injection in refbase to potentially read sensitive data or execute code via crafted parameters.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 28 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q338-298g-jhh7

## What is CVE-2015-6011?

CVE-2015-6011 is a medium-severity vulnerability in n/a, published on 28 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Web Reference Database (aka refbase) through 0.9.6 and bleeding-edge before 2015-01-08 allows remote attackers to conduct XML injection attacks via (1) the id parameter to unapi.php or (2) the stylesheet parameter to sru.php.

## Which versions are affected by CVE-2015-6011?

It affects 1 product.


Products: Refbase Refbase.

## How do I fix CVE-2015-6011?

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

## Is CVE-2015-6011 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-6008](https://insights.sbomify.com/CVE-2015-6008/): Command injection in n/a (high 7.5)
- [CVE-2015-6009](https://insights.sbomify.com/CVE-2015-6009/): SQL injection in n/a (high 7.5)
- [CVE-2015-7381](https://insights.sbomify.com/CVE-2015-7381/): Code injection in n/a (high 7.5)
- [CVE-2015-7382](https://insights.sbomify.com/CVE-2015-7382/): SQL injection in n/a (high 7.5)
- [CVE-2015-6007](https://insights.sbomify.com/CVE-2015-6007/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6011 and fix it if it is affected.

What it is: CVE-2015-6011 is a medium-severity vulnerability in n/a, published on 28 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6011 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-2015-6011/ (Markdown: https://insights.sbomify.com/CVE-2015-6011/index.md)
```

## Sources

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

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