# CVE-2010-3490: Path traversal in n/a

> Authenticated administrators can exploit a directory traversal flaw to create arbitrary PHP files, leading to remote code execution.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/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:** 28 Sep 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wrmq-cw6w-55hx

## What is CVE-2010-3490?

CVE-2010-3490 is a medium-severity path traversal vulnerability in Sangoma Freepbx, published on 28 Sep 2010. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Directory traversal vulnerability in page.recordings.php in the System Recordings component in the configuration interface in FreePBX 2.8.0 and earlier allows remote authenticated administrators to create arbitrary files via a .. (dot dot) in the usersnum parameter to admin/config.php, as demonstrated by creating a .php file under the web root.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2010-3490?

It affects 1 product.


Products: Sangoma Freepbx.

## How do I fix CVE-2010-3490?

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

## Is CVE-2010-3490 being exploited?

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

Public exploit code:

- FreePBX exploit <= 2.8.0 (github_poc): https://github.com/moayadalmalat/CVE-2010-3490
- FreePBX 2.8.0 - Recordings Interface Allows Remote Code Execution (exploitdb)

## Other vulnerabilities in Sangoma Freepbx

- [CVE-2025-57819](https://insights.sbomify.com/CVE-2025-57819/): Sangoma FreePBX Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2019-19006](https://insights.sbomify.com/CVE-2019-19006/): Sangoma FreePBX Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2026-73663](https://insights.sbomify.com/CVE-2026-73663/): FreePBX: Unauthenticated SQL injection in FreePBX missedcall via inbound Caller ID name leads to administrator takeover (critical 9.3)
- [CVE-2026-73665](https://insights.sbomify.com/CVE-2026-73665/): FreePBX UCP: Unauthenticated remote code execution via socket.io namespace auth bypass and AMI action injection (critical 9.3)
- [CVE-2026-46376](https://insights.sbomify.com/CVE-2026-46376/): FreePBX: Unauthenticated Use of Hard-Coded Credentials Vulnerability in FreePBX UCP Interface (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3490 and fix it if it is affected.

What it is: CVE-2010-3490 is a medium-severity path traversal vulnerability in Sangoma Freepbx, published on 28 Sep 2010. 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-2010-3490 exists.

Affected product: Sangoma Freepbx. 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-2010-3490/ (Markdown: https://insights.sbomify.com/CVE-2010-3490/index.md)
```

## Sources

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

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