# CVE-2003-1488: Auth bypass in n/a

> Remote attackers can bypass authentication in Truegalerie to gain administrator access by manipulating URL parameters.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-794w-3mfp-hppc

## What is CVE-2003-1488?

CVE-2003-1488 is a medium-severity authentication bypass vulnerability in n/a, published on 24 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The (1) verif_admin.php and (2) check_admin.php scripts in Truegalerie 1.0 allow remote attackers to gain administrator access via a request to admin.php without the connect parameter and with the loggedin parameter set to any value, such as 1.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2003-1488?

It affects 1 product.


Products: Truelogik Truegalerie.

## How do I fix CVE-2003-1488?

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

## Is CVE-2003-1488 being exploited?

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

Public exploit code:

- Truegalerie 1.0 - Unauthorized Administrative Access (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1488 and fix it if it is affected.

What it is: CVE-2003-1488 is a medium-severity authentication bypass vulnerability in n/a, published on 24 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1488 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-2003-1488/ (Markdown: https://insights.sbomify.com/CVE-2003-1488/index.md)
```

## Sources

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

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