# CVE-2003-0979: Other in n/a

> Remote attackers can abuse the guestbook as an open mail relay or delete the database by exploiting improper input escaping in VisitorBook LE.

- **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:** 11 Dec 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-pwm9-qhfp-646f

## What is CVE-2003-0979?

CVE-2003-0979 is a medium-severity vulnerability in n/a, published on 11 Dec 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FreeScripts VisitorBook LE (visitorbook.pl) does not properly escape line breaks in input, which allows remote attackers to (1) use VisitorBook as an open mail relay, when $mailuser is 1, via extra headers in the email field, or (2) cause the guestbook database to be deleted via a large number of line breaks that exceeds the $max_posts variable.

## Which versions are affected by CVE-2003-0979?

It affects 1 product.


Products: Freescripts Visitorbook.

## How do I fix CVE-2003-0979?

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

## Is CVE-2003-0979 being exploited?

There is no known exploitation of CVE-2003-0979 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2003-0980](https://insights.sbomify.com/CVE-2003-0980/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0979 and fix it if it is affected.

What it is: CVE-2003-0979 is a medium-severity vulnerability in n/a, published on 11 Dec 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0979 in the wild and no public exploit code.

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-2003-0979/ (Markdown: https://insights.sbomify.com/CVE-2003-0979/index.md)
```

## Sources

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

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