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

> Remote authenticated users can access administrative functions without proper privileges, potentially leading to unauthorized control.

- **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:** 9 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mqcc-6c28-c652

## What is CVE-2009-2393?

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

### Official description

admin/index.php in Virtuenetz Virtue Online Test Generator does not require administrative privileges, which allows remote authenticated users to have an unknown impact via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Virtuenetz Virtue Online Test Generator.

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

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

## Is CVE-2009-2393 being exploited?

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

Public exploit code:

- Virtue Online Test Generator - Authentication Bypass / SQL Injection / Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2392](https://insights.sbomify.com/CVE-2009-2392/): SQL injection in n/a (high 7.5)
- [CVE-2009-2391](https://insights.sbomify.com/CVE-2009-2391/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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