# CVE-2009-0457: Path traversal in n/a

> Remote attackers with admin access can execute arbitrary local files via directory traversal in AJA Portal modules.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7v98-4w7m-48mf

## What is CVE-2009-0457?

CVE-2009-0457 is a high-severity path traversal vulnerability in n/a, published on 6 Feb 2009. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in AJA Portal 1.2 allow remote attackers to include and execute arbitrary local files via directory traversal sequences in the currentlang parameter to admin/case.php in the (1) Contact_Plus and (2) Reviews modules, and (3) the module_name parameter to admin/includes/FANCYNLOptions.php in the Fancy_NewsLetter module.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Magtrb Aja Portal.

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

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

## Is CVE-2009-0457 being exploited?

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

Public exploit code:

- AJA Portal 1.2 (Windows) - Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0457 is a high-severity path traversal vulnerability in n/a, published on 6 Feb 2009. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0457 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-0457/ (Markdown: https://insights.sbomify.com/CVE-2009-0457/index.md)
```

## Sources

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

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