# CVE-2006-4546: Privilege escalation in n/a

> Authenticated administrators can escalate privileges to manage any list by modifying a parameter, allowing unauthorized administrative access.

- **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:** 6 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-22g8-9ph6-qpq3

## What is CVE-2006-4546?

CVE-2006-4546 is a medium-severity vulnerability in n/a, published on 6 Sep 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Lyris ListManager 8.95 allows remote authenticated users, who have administrative privileges for at least one list on the server, to add new administrators to any list via a modified MEMBERS_.List_ parameter.

## Which versions are affected by CVE-2006-4546?

It affects 1 product.


Products: Lyris List Manager.

## How do I fix CVE-2006-4546?

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

## Is CVE-2006-4546 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6319](https://insights.sbomify.com/CVE-2007-6319/): Privilege escalation in n/a (critical 10.0)
- [CVE-2005-4143](https://insights.sbomify.com/CVE-2005-4143/): SQL injection in n/a (high 7.5)
- [CVE-2005-4144](https://insights.sbomify.com/CVE-2005-4144/): SQL injection in n/a (high 7.5)
- [CVE-2006-4547](https://insights.sbomify.com/CVE-2006-4547/): Information disclosure in n/a (medium 6.5)
- [CVE-2000-0758](https://insights.sbomify.com/CVE-2000-0758/): Auth bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4546 and fix it if it is affected.

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

## Sources

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

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