# CVE-2007-2777: File upload in n/a

> Remote attackers with admin access can execute arbitrary PHP code via unrestricted file upload in AlstraSoft Template Seller Pro.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jg2m-4r5v-h2j3

## What is CVE-2007-2777?

CVE-2007-2777 is a high-severity vulnerability in n/a, published on 21 May 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in admin/addsptemplate.php in AlstraSoft Template Seller Pro 3.25 and earlier allows remote attackers to execute arbitrary PHP code via an arbitrary .php filename in the zip parameter, which is created under sptemplates/.

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

It affects 1 product.


Products: Alstrasoft Template Seller.

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

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

## Is CVE-2007-2777 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2777 exists.

Public exploit code:

- Alstrasoft Template Seller Pro 3.25 - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2776](https://insights.sbomify.com/CVE-2007-2776/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-4591](https://insights.sbomify.com/CVE-2006-4591/): Code injection in n/a (high 7.5)
- [CVE-2005-3797](https://insights.sbomify.com/CVE-2005-3797/): Code injection in n/a (high 7.5)
- [CVE-2005-3798](https://insights.sbomify.com/CVE-2005-3798/): SQL injection in n/a (high 7.5)
- [CVE-2006-0222](https://insights.sbomify.com/CVE-2006-0222/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2777 is a high-severity vulnerability in n/a, published on 21 May 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2777 exists.

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-2777/ (Markdown: https://insights.sbomify.com/CVE-2007-2777/index.md)
```

## Sources

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

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