# CVE-2007-3192: Missing authorization in n/a

> Remote attackers can read and modify configuration settings in JFFNMS by accessing admin/setup.php without authentication.

- **Severity:** Critical 9.4 (`AV:N/AC:L/Au:N/C:C/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gwpx-qg6m-mrg3

## What is CVE-2007-3192?

CVE-2007-3192 is a critical missing authorization vulnerability in n/a, published on 12 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

admin/setup.php in Just For Fun Network Management System (JFFNMS) 0.8.3 allows remote attackers to read and modify configuration settings via a direct request.

## Which versions are affected by CVE-2007-3192?

It affects 1 product.


Products: Jffnms Just for Fun Network Management System.

## How do I fix CVE-2007-3192?

Upgrade to a fixed version.

## Is CVE-2007-3192 being exploited?

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

Public exploit code:

- JFFNms 0.8.3 - 'admin/setup.php' Direct Request Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3191](https://insights.sbomify.com/CVE-2007-3191/): Information disclosure in n/a (critical 9.4)
- [CVE-2007-3204](https://insights.sbomify.com/CVE-2007-3204/): SQL injection in n/a (high 7.5)
- [CVE-2007-3190](https://insights.sbomify.com/CVE-2007-3190/): SQL injection in n/a (medium 6.8)
- [CVE-2007-3189](https://insights.sbomify.com/CVE-2007-3189/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3192 and fix it if it is affected.

What it is: CVE-2007-3192 is a critical missing authorization vulnerability in n/a, published on 12 Jun 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-2007-3192 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-2007-3192/ (Markdown: https://insights.sbomify.com/CVE-2007-3192/index.md)
```

## Sources

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

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