# CVE-2017-17651: SQL injection in n/a

> SQL injection in Paid To Read Script allows attackers to manipulate database queries via admin parameters, potentially exposing or altering data.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7vj5-jcwj-v84x

## What is CVE-2017-17651?

CVE-2017-17651 is a critical SQL injection vulnerability in n/a, published on 18 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Paid To Read Script 2.0.5 has SQL Injection via the admin/userview.php uid parameter, the admin/viewemcamp.php fnum parameter, or the admin/viewvisitcamp.php fn parameter.

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

## Which versions are affected by CVE-2017-17651?

It affects 1 product.


Products: Paid to Read Script Project Paid to Read Script.

## How do I fix CVE-2017-17651?

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

## Is CVE-2017-17651 being exploited?

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

Public exploit code:

- Paid To Read Script 2.0.5 - 'uid' / 'fnum' / 'fn' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-17777](https://insights.sbomify.com/CVE-2017-17777/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-17779](https://insights.sbomify.com/CVE-2017-17779/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17776](https://insights.sbomify.com/CVE-2017-17776/): Information disclosure in n/a (medium 5.3)
- [CVE-2017-17778](https://insights.sbomify.com/CVE-2017-17778/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17651 and fix it if it is affected.

What it is: CVE-2017-17651 is a critical SQL injection vulnerability in n/a, published on 18 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-17651 exists.

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-2017-17651/ (Markdown: https://insights.sbomify.com/CVE-2017-17651/index.md)
```

## Sources

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

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