# CVE-2006-4048: Auth bypass in n/a

> Remote attackers can bypass authentication and access the administration section by spoofing the administrator's IP address due to predictable session IDs.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-596j-78wx-m54g

## What is CVE-2006-4048?

CVE-2006-4048 is a high-severity authentication bypass vulnerability in n/a, published on 9 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netious CMS 0.4 initializes session IDs based on the client IP address, which allows remote attackers to gain access to the administration section when originating from the same IP address as the administrator.  NOTE: the provenance of this information is unknown; the details are obtained from third party information.

## Which versions are affected by CVE-2006-4048?

It affects 1 product.


Products: Netious Cms Netious Cms.

## How do I fix CVE-2006-4048?

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

## Is CVE-2006-4048 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4047](https://insights.sbomify.com/CVE-2006-4047/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4048 and fix it if it is affected.

What it is: CVE-2006-4048 is a high-severity authentication bypass vulnerability in n/a, published on 9 Aug 2006. 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-2006-4048 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-2006-4048/ (Markdown: https://insights.sbomify.com/CVE-2006-4048/index.md)
```

## Sources

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

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