# CVE-2025-29708: File upload in n/a

> Attackers can upload malicious files via the Create Services feature in Company Website CMS, potentially leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-jj4c-9qx7-h4pc

## What is CVE-2025-29708?

CVE-2025-29708 is a critical vulnerability in n/a, published on 16 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SourceCodester Company Website CMS 1.0 contains a file upload vulnerability via the "Create Services" file /dashboard/Services.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2025-29708?

It affects 1 product.


Products: Torrahclef Company Website Cms.

## How do I fix CVE-2025-29708?

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

## Is CVE-2025-29708 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-29709](https://insights.sbomify.com/CVE-2025-29709/): File upload in n/a (critical 9.8)
- [CVE-2025-13560](https://insights.sbomify.com/CVE-2025-13560/): SourceCodester Company Website CMS reset-password.php sql injection (medium 6.9)
- [CVE-2025-13561](https://insights.sbomify.com/CVE-2025-13561/): SourceCodester Company Website CMS index.php sql injection (medium 6.9)
- [CVE-2025-29710](https://insights.sbomify.com/CVE-2025-29710/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-29708 and fix it if it is affected.

What it is: CVE-2025-29708 is a critical vulnerability in n/a, published on 16 Apr 2025. 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-2025-29708 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-2025-29708/ (Markdown: https://insights.sbomify.com/CVE-2025-29708/index.md)
```

## Sources

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

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