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

> Authenticated administrators can upload and execute PHP files due to an incomplete blacklist in the FCKeditor module.

- **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:** 11 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4329-9f98-hhhp

## What is CVE-2007-2630?

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

### Official description

Incomplete blacklist vulnerability in filemanager/browser/default/connectors/php/config.php in the FCKeditor module, as used in ActiveCampaign 1-2-All (aka 12All) 4.50 through 4.53.13, and possibly other products, allows remote authenticated administrators to upload and possibly execute .php4 and .php5 files via unspecified vectors.  NOTE: this issue is reachable through filemanager/browser/default/browser.html.

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

It affects 1 product.


Products: Activecampaign 1-2-All Broadcast Email.

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

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

## Is CVE-2007-2630 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3679](https://insights.sbomify.com/CVE-2005-3679/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2630 is a medium-severity vulnerability in n/a, published on 11 May 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2630 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-2630/ (Markdown: https://insights.sbomify.com/CVE-2007-2630/index.md)
```

## Sources

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

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