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

> Remote attackers can bypass authentication to delete and recreate the authentication file, creating a new admin account in JBC Explorer.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 10 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g29r-hmvv-w2p4

## What is CVE-2007-5913?

CVE-2007-5913 is a medium-severity missing authorization vulnerability in n/a, published on 10 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

dirsys/modules/auth.php in JBC Explorer 7.20 RC1 and earlier does not require authentication, which allows remote attackers to (1) delete auth.inc.php via the suppr parameter, and (2) re-create the auth.inc.php file with contents that specify a new account name and password for JBC Explorer via the login and password parameters.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Jean Charles Jbc Explorer.

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

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

## Is CVE-2007-5913 being exploited?

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

Public exploit code:

- JBC Explorer 7.20 RC 1 - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5914](https://insights.sbomify.com/CVE-2007-5914/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5913 is a medium-severity missing authorization vulnerability in n/a, published on 10 Nov 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-5913 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-5913/ (Markdown: https://insights.sbomify.com/CVE-2007-5913/index.md)
```

## Sources

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

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