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

> Remote attackers can execute arbitrary SQL commands via the id parameter in pop_profile.asp, potentially compromising forum data.

- **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:** 21 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p77g-x9v2-6rcp

## What is CVE-2007-1023?

CVE-2007-1023 is a high-severity SQL injection vulnerability in n/a, published on 21 Feb 2007. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in pop_profile.asp in Snitz Forums 2000 3.1 SR4 allows remote attackers to execute arbitrary SQL commands via the id parameter.

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

It affects 1 product.


Products: Snitz Communications Snitz Forums 2000.

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

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

## Is CVE-2007-1023 being exploited?

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

Public exploit code:

- Snitz Forums 2000 3.1 SR4 - 'pop_profile.asp' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0493](https://insights.sbomify.com/CVE-2003-0493/): Auth bypass in n/a (critical 10.0)
- [CVE-2003-0494](https://insights.sbomify.com/CVE-2003-0494/): Auth bypass in n/a (critical 10.0)
- [CVE-2006-5603](https://insights.sbomify.com/CVE-2006-5603/): SQL injection in n/a (critical 9.8)
- [CVE-2012-5313](https://insights.sbomify.com/CVE-2012-5313/): SQL injection in n/a (high 7.5)
- [CVE-2010-4826](https://insights.sbomify.com/CVE-2010-4826/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1023 is a high-severity SQL injection vulnerability in n/a, published on 21 Feb 2007. 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-2007-1023 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-1023/ (Markdown: https://insights.sbomify.com/CVE-2007-1023/index.md)
```

## Sources

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

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