# CVE-2007-3256: Other in n/a

> Authenticated users can set arbitrary Content-Type headers on documents, potentially facilitating malware distribution in Xythos products.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xwm7-qf33-7c64

## What is CVE-2007-3256?

CVE-2007-3256 is a medium-severity vulnerability in n/a, published on 27 Jun 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Xythos Enterprise Document Manager (XEDM), Digital Locker (XDL), and possibly WebFile Server before 6.0.46.1 allow remote authenticated users to associate arbitrary Content-Type HTTP headers with documents, which might facilitate malware distribution.

## Which versions are affected by CVE-2007-3256?

It affects 3 products.


Products: Xythos Digital Locker, Xythos Enterprise Document Manager, Xythos Webfile Server.

## How do I fix CVE-2007-3256?

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

## Is CVE-2007-3256 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3256 and fix it if it is affected.

What it is: CVE-2007-3256 is a medium-severity vulnerability in n/a, published on 27 Jun 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3256 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-2007-3256/ (Markdown: https://insights.sbomify.com/CVE-2007-3256/index.md)
```

## Sources

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

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