# CVE-2007-10001: web-cyradm search.php sql injection

> An attacker can perform SQL injection via the searchstring argument in web-cyradm, potentially reading or modifying database contents.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-54q9-gr43-5wv9

## What is CVE-2007-10001?

CVE-2007-10001 is a low-severity SQL injection vulnerability in web-cyradm, published on 5 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in web-cyradm. This affects an unknown part of the file search.php. The manipulation of the argument searchstring leads to sql injection. It is recommended to apply a patch to fix this issue. The identifier VDB-217449 was assigned to this vulnerability.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Web-Cyradm Project Web-Cyradm.

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

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

## Is CVE-2007-10001 being exploited?

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

## Other vulnerabilities in web-cyradm

- [CVE-2007-10002](https://insights.sbomify.com/CVE-2007-10002/): web-cyradm auth.inc.php sql injection (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-10001 is a low-severity SQL injection vulnerability in web-cyradm, published on 5 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-10001 in the wild and no public exploit code.

Affected product: web-cyradm. 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-10001/ (Markdown: https://insights.sbomify.com/CVE-2007-10001/index.md)
```

## Sources

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

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