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

> Remote attackers can perform administrative actions like editing or deleting content without authentication due to missing checks in admin.php.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 6 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-68fg-4qvx-c25f

## What is CVE-2007-3611?

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

### Official description

admin.php in VRNews 1.1.1, and possibly other 1.x versions, does not require authentication, which allows remote attackers to perform certain administrative actions via a direct request with a (1) edit, (2) add, (3) config, or (4) del value in the act parameter.

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

It affects 1 product.


Products: Vrnews Vrnews.

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

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

## Is CVE-2007-3611 being exploited?

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

Public exploit code:

- VRNews 1.1.1 - 'admin.php' Remote Security Bypass (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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