# CVE-2006-5037: Server-side request forgery in n/a

> Remote attackers can exploit MySource Matrix as an HTTP proxy to access arbitrary sites and conduct XSS attacks via the sq_content_src parameter.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 27 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-723w-74pm-v4fj

## What is CVE-2006-5037?

CVE-2006-5037 is a medium-severity server-side request forgery vulnerability in n/a, published on 27 Sep 2006. 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

MySource Matrix after 3.8 allows remote attackers to use the application as an HTTP proxy server via a MIME encoded URL in the sq_content_src parameter to access arbitrary sites with the server's IP address and conduct cross-site scripting (XSS) attacks.  NOTE: the researcher reports that "The vendor does not consider this a vulnerability.

## Which versions are affected by CVE-2006-5037?

It affects 1 product.


Products: Squiz Mysource Matrix.

## How do I fix CVE-2006-5037?

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

## Is CVE-2006-5037 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4901](https://insights.sbomify.com/CVE-2010-4901/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5037 and fix it if it is affected.

What it is: CVE-2006-5037 is a medium-severity server-side request forgery vulnerability in n/a, published on 27 Sep 2006. 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-2006-5037 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-2006-5037/ (Markdown: https://insights.sbomify.com/CVE-2006-5037/index.md)
```

## Sources

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

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