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

> Remote attackers can modify admin credentials in Guestbara by manipulating parameters, leading to full administrative account takeover.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rp6c-mxw5-wc9m

## What is CVE-2007-1553?

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

### Official description

admin/configuration.php in Guestbara 1.2 and earlier allows remote attackers to modify the e-mail, name, and password of the admin account by setting the zapis parameter to "ok" and providing modified admin_mail, login, and pass parameters.

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

It affects 1 product.


Products: Guestbara Guestbara.

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

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

## Is CVE-2007-1553 being exploited?

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

Public exploit code:

- Guestbara 1.2 - Change Admin Login and Password (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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