# CVE-2020-37081: Fishing Reservation System 7.5 - 'uid' SQL Injection

> Attackers can inject malicious SQL commands via vulnerable parameters in admin, cart, and calendar scripts to compromise the database and application.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-58j8-gxpr-8cgq

## What is CVE-2020-37081?

CVE-2020-37081 is a high-severity SQL injection vulnerability in Fishing Reservation System, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Fishing Reservation System 7.5 contains multiple remote SQL injection vulnerabilities in admin.php, cart.php, and calendar.php that allow attackers to inject malicious SQL commands. Attackers can exploit vulnerable parameters like uid, pid, type, m, y, and code to compromise the database management system and web application without user interaction.

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

## Which versions are affected by CVE-2020-37081?


## How do I fix CVE-2020-37081?

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

## Is CVE-2020-37081 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37081 and fix it if it is affected.

What it is: CVE-2020-37081 is a high-severity SQL injection vulnerability in Fishing Reservation System, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37081 exists.

Affected product: Fishing Reservation System. 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-2020-37081/ (Markdown: https://insights.sbomify.com/CVE-2020-37081/index.md)
```

## Sources

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

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