# CVE-2002-1719: Missing authorization in n/a

> Remote attackers can modify posted messages in the Bavo web application due to an unknown vulnerability.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xqgx-39jh-mw57

## What is CVE-2002-1719?

CVE-2002-1719 is a medium-severity missing authorization vulnerability in n/a, published on 21 Jun 2005. It can be exploited over the network.

### Official description

Unknown vulnerability in Bavo 0.3 allows remote attackers to modify posted messages.

## Which versions are affected by CVE-2002-1719?

It affects 1 product.


Products: Bavo Bavo.

## How do I fix CVE-2002-1719?

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

## Is CVE-2002-1719 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1719 and fix it if it is affected.

What it is: CVE-2002-1719 is a medium-severity missing authorization vulnerability in n/a, published on 21 Jun 2005. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2002-1719 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-2002-1719/ (Markdown: https://insights.sbomify.com/CVE-2002-1719/index.md)
```

## Sources

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

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