# CVE-2009-1825: Missing authorization in n/a

> Remote authenticated users can list user accounts in myColex due to missing administrative authentication checks in the admin module.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **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:** 29 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jpcm-68c4-6rr4

## What is CVE-2009-1825?

CVE-2009-1825 is a medium-severity missing authorization vulnerability in n/a, published on 29 May 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

modules/admuser.php in myColex 1.4.2 does not require administrative authentication, which allows remote authenticated users to list user accounts via a Find action.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2009-1825?

It affects 1 product.


Products: Collector Mycolex.

## How do I fix CVE-2009-1825?

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

## Is CVE-2009-1825 being exploited?

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

Public exploit code:

- my-colex 1.4.2 - Authentication Bypass / SQL Injection / Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-1810](https://insights.sbomify.com/CVE-2009-1810/): SQL injection in n/a (medium 6.0)
- [CVE-2009-1809](https://insights.sbomify.com/CVE-2009-1809/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1825 and fix it if it is affected.

What it is: CVE-2009-1825 is a medium-severity missing authorization vulnerability in n/a, published on 29 May 2009. 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-2009-1825 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-2009-1825/ (Markdown: https://insights.sbomify.com/CVE-2009-1825/index.md)
```

## Sources

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

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