# CVE-2012-4869: Command injection in n/a

> Remote attackers can execute arbitrary commands via the callmenum parameter in FreePBX's callme_page.php script.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vmpf-f73j-fg6v

## What is CVE-2012-4869?

CVE-2012-4869 is a high-severity command injection vulnerability in Sangoma Freepbx, published on 6 Sep 2012. It can be exploited over the network, with no action from the victim.

### Official description

The callme_startcall function in recordings/misc/callme_page.php in FreePBX 2.9, 2.10, and earlier allows remote attackers to execute arbitrary commands via the callmenum parameter in a c action.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2012-4869?

It affects 1 product.


Products: Sangoma Freepbx.

## How do I fix CVE-2012-4869?

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

## Is CVE-2012-4869 being exploited?

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

Public exploit code:

- FreePBX 2.10.0 / 2.9.0 callmenum Remote Code Execution (metasploit)
- FreePBX 2.9.0/2.10.0 - Multiple Vulnerabilities (exploitdb)
- FreePBX 2.10.0 / Elastix 2.2.0 - Remote Code Execution (exploitdb)
- FreePBX 2.9.0/2.10.0 - 'callmenum' Remote Code Execution (Metasploit) (exploitdb)
- https://github.com/cyberdesu/Elastix-2.2.0-CVE-2012-4869 (github_poc): https://github.com/cyberdesu/Elastix-2.2.0-CVE-2012-4869

## 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-2012-4869 and fix it if it is affected.

What it is: CVE-2012-4869 is a high-severity command injection vulnerability in Sangoma Freepbx, published on 6 Sep 2012. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4869 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-2012-4869/ (Markdown: https://insights.sbomify.com/CVE-2012-4869/index.md)
```

## Sources

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

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