# CVE-2002-1879: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via vulnerable parameters in LokwaBB, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-26hr-9q73-x3wm

## What is CVE-2002-1879?

CVE-2002-1879 is a high-severity SQL injection vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in LokwaBB 1.2.2 allows remote attackers to execute arbitrary SQL commands via the (1) member parameter to member.php or (2) loser parameter to misc.php.

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

It affects 1 product.


Products: Lokwa Lokwabb.

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

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

## Is CVE-2002-1879 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1880](https://insights.sbomify.com/CVE-2002-1880/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1879 is a high-severity SQL injection vulnerability in n/a, published on 28 Jun 2005. 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-2002-1879 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-1879/ (Markdown: https://insights.sbomify.com/CVE-2002-1879/index.md)
```

## Sources

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

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