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

> Remote attackers can bypass authentication in Digi-news admin.php by setting a specific cookie, gaining administrative access without a password.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2016
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-644p-86mq-w7cq

## What is CVE-2003-0588?

CVE-2003-0588 is a critical authentication bypass vulnerability in n/a, published on 17 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

admin.php in Digi-news 1.1 allows remote attackers to bypass authentication via a cookie with the username set to the name of the administrator, which satisfies an improper condition in admin.php that does not require a correct password.

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

It affects 1 product.


Products: Digi-Fx Digi-News.

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

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

## Is CVE-2003-0588 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0589](https://insights.sbomify.com/CVE-2003-0589/): Auth bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0588 is a critical authentication bypass vulnerability in n/a, published on 17 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0588 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-2003-0588/ (Markdown: https://insights.sbomify.com/CVE-2003-0588/index.md)
```

## Sources

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

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