# CVE-2018-25072: lojban jbovlaste listing.html sql injection

> Remote attackers can exploit SQL injection in the listing page to read or modify database contents.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2023
- **Updated:** 25 Nov 2024
- **Also known as:** GHSA-7rfx-rjq2-9f9r

## What is CVE-2018-25072?

CVE-2018-25072 is a medium-severity SQL injection vulnerability in lojban jbovlaste, published on 8 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in lojban jbovlaste. This affects an unknown part of the file dict/listing.html. The manipulation leads to sql injection. It is possible to initiate the attack remotely. The patch is named 6ff44c2e87b1113eb07d76ea62e1f64193b04d15. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217647.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2018-25072?

It affects 1 product.


Products: Lojban Jbovlaste.

## How do I fix CVE-2018-25072?

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

## Is CVE-2018-25072 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25072 and fix it if it is affected.

What it is: CVE-2018-25072 is a medium-severity SQL injection vulnerability in lojban jbovlaste, published on 8 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-25072 in the wild and no public exploit code.

Affected product: lojban jbovlaste. 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-2018-25072/ (Markdown: https://insights.sbomify.com/CVE-2018-25072/index.md)
```

## Sources

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

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