# CVE-2026-62362: PeerBanHelper: SQL injection via ${field} interpolation in MyBatis mapper for analysis endpoint

> An authenticated attacker can exploit SQL injection in the analysis endpoint to read all data from the PeerBanHelper database.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-pc89-mfwm-hj9x

## What is CVE-2026-62362?

CVE-2026-62362 is a medium-severity SQL injection vulnerability in PBH-BTN PeerBanHelper, published on 16 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

PeerBanHelper automatically blocks unwanted, leeching, and abnormal BitTorrent peers using customizable and cloud rules. From 5.0.0 until 9.3.15, the /api/statistic/analysis/field endpoint accepts a crafted field query parameter from an authenticated user and passes it to countField or sumField. The mapField() method forwards unrecognized field names without sanitization, so unrecognized field names are interpolated into SQL through ${field} across the SQLite, MySQL, and PostgreSQL mappers. Successful exploitation can read all data in the PeerBanHelper database. This issue is fixed in version 9.3.15.

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

## Which versions are affected by CVE-2026-62362?


## How do I fix CVE-2026-62362?

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

## Is CVE-2026-62362 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62362 and fix it if it is affected.

What it is: CVE-2026-62362 is a medium-severity SQL injection vulnerability in PBH-BTN PeerBanHelper, published on 16 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62362 exists.

Affected product: PBH-BTN PeerBanHelper. 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-2026-62362/ (Markdown: https://insights.sbomify.com/CVE-2026-62362/index.md)
```

## Sources

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

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