# CVE-2007-3013: SQL injection in n/a

> Authenticated users with edit permissions can execute arbitrary SQL commands via the id parameter in activeWeb contentserver.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8gvv-4642-9f2m

## What is CVE-2007-3013?

CVE-2007-3013 is a medium-severity SQL injection vulnerability in n/a, published on 15 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in activeWeb contentserver before 5.6.2964 allows remote authenticated users with edit permission to execute arbitrary SQL commands via the id parameter to admin/picture/picture_real_edit.asp, and probably other unspecified vectors.

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

It affects 1 product.


Products: Activeweb Contentserver.

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

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

## Is CVE-2007-3013 being exploited?

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

Public exploit code:

- ActiveWeb Contentserver 5.6.2929 - 'Picture_Real_Edit.asp' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3014](https://insights.sbomify.com/CVE-2007-3014/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2007-3017](https://insights.sbomify.com/CVE-2007-3017/): Cross-site scripting in n/a (medium 4.0)
- [CVE-2007-3018](https://insights.sbomify.com/CVE-2007-3018/): Path traversal in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3013 is a medium-severity SQL injection vulnerability in n/a, published on 15 Jul 2007. Any signed-in user can exploit it 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-2007-3013 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-3013/ (Markdown: https://insights.sbomify.com/CVE-2007-3013/index.md)
```

## Sources

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

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