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

> Remote attackers can change arbitrary usernames and passwords in Snaps! Gallery by exploiting missing authorization checks in the admin user editing interface.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fr3w-j4xg-gwmq

## What is CVE-2007-2715?

CVE-2007-2715 is a critical missing authorization vulnerability in n/a, published on 16 May 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Admin/users.php in Snaps! Gallery 1.4.4 allows remote attackers to change arbitrary usernames and passwords via the (1) username, or the (2) password and password2 parameters in an edit action.

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

It affects 1 product.


Products: Snaps Gallery Snaps Gallery.

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

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

## Is CVE-2007-2715 being exploited?

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

Public exploit code:

- Snaps! Gallery 1.4.4 - Remote User Pass Change (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2715 is a critical missing authorization vulnerability in n/a, published on 16 May 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2715 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-2715/ (Markdown: https://insights.sbomify.com/CVE-2007-2715/index.md)
```

## Sources

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

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