# CVE-2007-4600: Security feature bypass in n/a

> Attackers can bypass worksheet protection in Mathcad by removing a specific XML element, allowing unauthorized access to protected content.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x2j4-38c3-gpq4

## What is CVE-2007-4600?

CVE-2007-4600 is a medium-severity vulnerability in n/a, published on 18 Oct 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The "Protect Worksheet" functionality in Mathsoft Mathcad 12 through 13.1, and PTC Mathcad 14, implements file access restrictions via a protection element in a gzipped XML file, which allows attackers to bypass these restrictions by removing this element.

Weakness: CWE-264

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

It affects 1 product.


Products: Ptc Mathcad.

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

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

## Is CVE-2007-4600 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4600 is a medium-severity vulnerability in n/a, published on 18 Oct 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-4600 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-4600/ (Markdown: https://insights.sbomify.com/CVE-2007-4600/index.md)
```

## Sources

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

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