# CVE-2017-17952: Business logic in n/a

> Attackers can register accounts using spoofed emails due to predictable registration URLs, potentially leading to unauthorized account access.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vq8m-m9v5-x26g

## What is CVE-2017-17952?

CVE-2017-17952 is a high-severity vulnerability in n/a, published on 28 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP Scripts Mall PHP Multivendor Ecommerce has a predicable registration URL, which makes it easier for remote attackers to register with an invalid or spoofed e-mail address.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Php Multivendor Ecommerce Project Php Multivendor Ecommerce.

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

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

## Is CVE-2017-17952 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17951](https://insights.sbomify.com/CVE-2017-17951/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17957](https://insights.sbomify.com/CVE-2017-17957/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17959](https://insights.sbomify.com/CVE-2017-17959/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17624](https://insights.sbomify.com/CVE-2017-17624/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17960](https://insights.sbomify.com/CVE-2017-17960/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17952 is a high-severity vulnerability in n/a, published on 28 Dec 2017. 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-2017-17952 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-2017-17952/ (Markdown: https://insights.sbomify.com/CVE-2017-17952/index.md)
```

## Sources

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

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